As an example of what Theo notes here (that REST can used for updates
as well as read-only), those of you wanting to see a RESTful API in
action may want to look at Twitter's documentation of their REST API:
http://apiwiki.twitter.com/REST+API+Documentation
It works in both directions.
Regards,
Dan
On Nov 1, 2008, at 11:24 PM, Theo Zourzouvillys wrote:
On Fri, Oct 31, 2008 at 5:54 PM, <[EMAIL PROTECTED]> wrote:
The REST model seems to be oriented toward "read-only" access, where
the data is expected to flow from the server to the client, whereas
the ACH problem has data flowing from the client (UA) to the server
(proxy), which is what leads to most of the problems.
Not at all; the REST model uses the PUT, POST, and DELETE HTTP verbs
for creation/manipulation of resources.
~ Theo
--
Theo Zourzouvillys
Chief Technical Officer
VoIP.co.uk - Commerce House, Telford Road, Bicester, OX26 4LD
Tel: +44 1908 764 196
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss
--
Dan York, CISSP, Director of Emerging Communication Technology
Office of the CTO Voxeo Corporation [EMAIL PROTECTED]
Phone: +1-407-455-5859 Skype: danyork http://www.voxeo.com
Blogs: http://blogs.voxeo.com http://www.disruptivetelephony.com
Build voice applications based on open standards.
Find out how at http://www.voxeo.com/free
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss
