Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: http or TCP-IP



Permlink Replies: 1 - Last Post: Aug 24, 2015 11:00 AM Last Post By: Cesar Romero
Flavio Elorza

Posts: 1
Registered: 4/8/10
http or TCP-IP
Click to report abuse...   Click to reply to this thread Reply
  Posted: Aug 13, 2015 1:16 PM
What is the decision to choose the best protocol (TCP or HTTP) for a DataSnap service?

Thanks
Cesar Romero


Posts: 462
Registered: 3/22/00
Re: http or TCP-IP
Click to report abuse...   Click to reply to this thread Reply
  Posted: Aug 24, 2015 11:00 AM   in response to: Flavio Elorza in response to: Flavio Elorza
Flavio Elorza wrote:

What is the decision to choose the best protocol (TCP or HTTP) for a
DataSnap service?

From Marco Cantù White paper "Development and Deployment of Delphi
Multi-tier Applications, December 2012"

<quote>
• A TCP/IP connection component (DSTCPServerTransport), offering a
state-full and stable connection to the clients. This is generally
suited for an internal network, but given the recent addition of
connection monitoring capabilities could also be deployed to the
Internet as a whole. The socket-based connections offer custom data
compression and data encryption, through filters that must be deploying
on both the server and the client. This model makes sense only if the
client application is also written in Delphi or C++Builder.

• An HTTP connection component (DSHTTPService), offering a state-full
connection on top of a stateless protocol, though custom session
management and the ability of keep server side object active in the
session (as described later). Again, this is mostly meant to be used
when the client is also a Delphi or C++Builder application, and can use
the HTTPS protocol for extra security.

• A REST connection, based either on the same HTTP connection component
described above or on the integration of the DataSnap server with the
WebBroker architecture (which offers deployment as an IIS module or
stand-alone web servers). In both cases the DataSnap server behaves as
a stateless server, and there is much more flexibility in terms of the
development tools you can use to build the client applications. This is
likely the most open, flexible, and scalable option and the one I’ll
keep my focus for most of the paper.

</quote>

Regards,

Cesar Romero

Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02