I cut the 1.0 branch of the lib last night. On DELETE or POST an ETag header will be returned to the Server. There's "before" and "after" events for all HTTP actions, as well as undocumented "beforeXHR" and "afterXHR" for specific developer use cases, e.g. if you need to track when a resource is accessed regardless of intent.
The 1.0 docs are live at http://abaaso.com now, you can get the full api by accessing /api The interface supports HTML, JSON & XML output. simply append /json or /xml to the end of the API URI to get the format you want. You can do /api, /api/(command or format) and /api/(command)/(format). I'll be working on tech demos over the next few weeks before I dive into the 1.1 widgets and refactoring. If there's any features you'd like to see that aren't in the 1.1 road map, just let me know. On Jan 11, 4:05 pm, jmulligan <[email protected]> wrote: > Hi, > > So this morning marks my start of removing the extra try/catches and > correcting regressions such as el.clear(). I'm expecting to have the > documentation system for abaaso.com in place this weekend or next, and > that will have some samples to start. More would follow as time passes > and I build more apps & widgets. > > Since there hasn't been any feedback on my implementation of HATEOAS, > anyone reading this thread wondering what the heck "HATEOAS" is should > pick up REST in Practice (O'Reilly). The acronym describes a Level > Three application/service; meaning the client is driven by the service > responses. > > Seehttp://www.flickr.com/photos/deviation/5346611445/for a graphic / > high level explanation -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
