On Mon, Aug 11, 2008 at 9:47 PM, Rickard Öberg <[EMAIL PROTECTED]> wrote:
> /entity - listing of all Entities
I think this one is a bad idea. Perhaps if some "development" mode is
enabled, but not generally available (a lot of apps won't need
security to stop it either).
> /entity/<type> - listing of all Entities of the given type
This one can be equally dangerous in production environments.
Perhaps both of the above must be explicitly enabled per type, and/or
a limit to how many instances to serve.
> /entity/<type>/<id>.html - form for editing a specific Entity
> /entity/<type>/<id>.rdf - RDF view of the specific Entity
Personally, I don't like file extensions, especially from the days of
IE implying so much from them (not sure what IE does nowadays). I
guess that a path element is more REST-friendly than query arguments,
so I would go for that.
> and then:
> /type - listing of all Entity Types
Ok.
> /type/<type>.rdf - RDF schema for the Entity Type
Again, should we have the .rdf extension?
/type/org.qi4j.rest.test.TestEntity.rdf
vs
/type/org.qi4j.rest.test.TestEntity
Cheers
Niclas
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
