Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Create, Update and Delete of OData entities #30

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment
Open

Support Create, Update and Delete of OData entities #30

GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link
Collaborator

Currently such operations return "not implemented" by GeoREST.

Original issue reported on code.google.com by jumpinja...@gmail.com on 17 Jan 2012 at 10:18

@GoogleCodeExporter
Copy link
Collaborator Author

I think this is a great idea, but at a minimum would want to be able to set the 
default access level to read-only on a per-featureset basis.  

Ideally, we would also support authentication and authorization for OData, but 
that feels like a lot of work.  Not sure if authentication  could be handled at 
the HTTP level; guess it depends on order of modules in IIS, not sure for 
Apache.  There would still need to be some way of tieing in authorization.

Original comment by ja...@jasonbirch.com on 17 Jan 2012 at 8:56

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant