On 6/7/06, M. David Peterson <[EMAIL PROTECTED]> wrote:
In what should be fairly obvious, I am using file extensions to represent the action that is desired to take place upon the atom feed. for .omx extensions only GET and HEAD are allowed, for .atom only GET, for .update, only POST, .create, only PUT, and .delete, only DELETE. This adds a layer of "obvious" to the action that is taking place (or at very least is being requested to take place.) This will allow for a fairly simple and straightforward way to access, edit, update, and delete a particular atom feed, or entry contained within that feed. For example, http://extf.net/blog/2006/06/01/This_Is_An_Entry.create would create the entry in the folder 2006/06/01/This_Is_An_Entry, http://extf.net/blog/2006/06/01/This_Is_An_Entry.update would update that same entry, http://extf.net/blog/2006/06/01/This_Is_An_Entry.atom would return a copy of the atom feed for that entry, and http://extf.net/blog/2006/06/01/This_Is_An_Entry.delete would delete that entry.
If I understand this correctly I think you have a problem. In the APP there is only one URI for an entry specified, the edit URI returned either via the Location: header or in the feed via the link/@rel='edit' member, and that URI needs to be able to handle GET, PUT, and DELETE. -joe -- Joe Gregorio http://bitworking.org
