On Tue, 7 Jun 2011, ik wrote:
On Tue, Jun 7, 2011 at 20:54, Michael Van Canneyt
wrote:
On Tue, 7 Jun 2011, ik wrote:
As you know REST is an architecture, not just a set of classes
or methods.
REST doesn't even require HTTP. So calling a webserver c
On Tue, Jun 7, 2011 at 20:54, Michael Van Canneyt wrote:
>
>
> On Tue, 7 Jun 2011, ik wrote:
>
> As you know REST is an architecture, not just a set of classes or
>> methods.
>> REST doesn't even require HTTP. So calling a webserver class
>> RESTsomething
>> because onGet, onPut, e
On Tue, 7 Jun 2011, ik wrote:
As you know REST is an architecture, not just a set of classes or methods.
REST doesn't even require HTTP. So calling a webserver class RESTsomething
because onGet, onPut, etc. are exposed does not have any added value.
>I agree. This was why I
On Tue, Jun 7, 2011 at 17:49, wrote:
>
>
> On Tue, 7 Jun 2011, Ludo Brands wrote:
>
> Ok, that is simply an alternative to the current
>>> TFPWebDataModule which does
>>> not rely on part of the URL to determine the CRUD action, but
>>> uses the URL
>>> just to determine the resource, and the HT
On Tue, 7 Jun 2011, Ludo Brands wrote:
Ok, that is simply an alternative to the current
TFPWebDataModule which does
not rely on part of the URL to determine the CRUD action, but
uses the URL
just to determine the resource, and the HTTP method to see
which CRUD action
needs to be performed.
Th
> Ok, that is simply an alternative to the current
> TFPWebDataModule which does
> not rely on part of the URL to determine the CRUD action, but
> uses the URL
> just to determine the resource, and the HTTP method to see
> which CRUD action
> needs to be performed.
>
> That's easily done. It
On Tue, 7 Jun 2011, Ludo Brands wrote:
TCP is the transport layer, HTTP the application layer. Don't know what a
REST *transport layer* is, but i can guess what your question is about.
Well, I consider HTTP part of the the transport layer. The messages could be
transported over SMTP, after a
