cool, how much is the bounty?On Tue, May 27, 2008 at 10:42 AM, EdPimentl <edpimentl@gmail.com> wrote:_______________________________________________I am putting a bounty to add RESTful WebServices in FreeSwitch.
The bounty ask that TONIC is use as the RESTful Framework.
TONIC should then be use to create simple CALLback application and establish ad-hoc VoiceConference.
To those not familiar with TONIC here is write up.Tonic A RESTful Web App Development Framework
Tonic is an open source less is more, RESTful Web application development and Web site management PHP script designed to do things "the right way", where resources are king and the framework gets out of the way and leaves the developer to get on with it.
Tonic helps you develop Web applications that embrace the way the Web really works, enabling your applications to scale, extend and work with other systems easily.
- Everything is a resource
- Tonic works exclusively with resources, a resource is simply a piece of data with some metadata accessable by a URL using HTTP methods. Everything within a Tonic system is a resource and so can be handled via the standard HTTP interface.
- Domain modelling through resources
- When modelling your problem domain within a Tonic system, every domain object is a resource or a collection of resources.
- Keep it simple, stupid!
- Following the Unix philosophy of many small parts working together via a common interface, Tonic uses resources as it's "programs" and HTTP as it's "streams" to enable you to build complexity out of simplicity.
Main features
Tonic embraces a number of standard Web features and best practices, as well as features, principles and ideas taken from PHP, Unix, and other software design patterns:
- Resource editing via HTTP PUT and DELETE methods (or via the Resource::save() and Resource::remove() PHP methods)
- Easy to extend via new resource classes
- HTTP basic and digest authentication
- Resource method permissions to provide authorisation to individual resource methods
- Output templating via Smarty
- Output caching via HTTP 304 response codes and modified headers
- Extendable resource storage types via adapters
- Content negotiation
- Match multiple URLs to a single resource
- Follows Unix modular design principles
And here is why everything one does or will do, should be done via RESTFul messaging..
Think about it, Google, AMAZON, YAHOO have standardized on REST.
http://www.infoq.com/articles/rest-introduction
http://wiki.opengarden.org/REST/REST_for_the_Rest_of_Us
http://en.wikipedia.org/wiki/Representational_State_Transfer
http://rest.blueoxen.net/cgi-bin/wiki.pl?FrontPage
http://www.jibbering.com/2002/4/httprequest.html
http://java.sun.com/developer/technicalArticles/WebServices/restful/
http://www.ics.uci.edu/~fielding/pubs/dissertation/software_arch.htm#sec_1_2 ******
-E
http://mobiquity.ws
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
--
Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
iax:guest@conference.freeswitch.org/888
googletalk:conf+888@conference.freeswitch.org
pstn:213-799-1400