2016-09-12 8:27 GMT-04:00 Benoît Minisini <gam...@users.sourceforge.net>:

> Why don't you just create a text file in the "Project" folder and use it
> as writing pad?
>
well benout have right!

2016-09-10 3:33 GMT-04:00 Christof Thalhofer <chri...@deganius.de>:

> Please correct me if I'm wrong: REST came later and as I can see, the
> upcoming of REST ist somewhat an answer to the extreme complexity of SOAP.
>
yes! i mean in the REST context of course.


>
> For a REST webservice you need a good tutorial, but not really a
> framework. The only thing that is needed for REST is a router that maps
> url paths to functions and sends back the result via HTTP. The result
> can be anything, a file, an integer, a Json string, whatever.
>
so then benoit now Christof ilustrate it!


> A router does a mapping like this:
> <snip>
> > Method     URL                     Action
> > GET        /api/todos              Retrieve all todos
> > GET        /api/todos/search/bug   Search for todos with ‘bug’ in their
> name
> > GET        /api/todo/1             Retrieve todo with id == 1
> > POST       /api/todo               Add a new todo
> > PUT        /api/todo/1             Update todo with id == 1
> > DELETE     /api/todo/1             Delete todo with id == 1
> <snap>
>



> My understanding: If you do REST it would be somewhat easy, if you do
> SOAP it would be horrible.
>
So then lets discard the SOAP compability!
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
Gambas-user mailing list
Gambas-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gambas-user

Reply via email to