Re: ANN: RTC SDK 1.9g > New Message-based Third-party transports

"Hannes Danzl[NDD]" wrote:
Danijel Tkalcec wrote:

Triggered by a recent discussion in another thread, new components for
using
Message-based Third-party transports have been added to the
RealThinClient
SDK, with a ready-to-use set of plugging which allow tunneling of all RTC
communication through NexusDB components (Client and Server).

Coool! Do you have any early performance results? Is it as fast as the
original ones?

I have done some performance tests with client and server components in one
app (direct link, NexusDB Memory transport and NexusDB WinSock transport),
with extremely good results. I have to say, I was really amazed by how fast
NexusDB transports perform ... especially the WinSock NexusDB transport,
which uses blocking IOCP.

Performance gains when using NexusDB transports enormous and I'm starting to
think about adding a binary protocol for the RTC SDK, since you can't
achieve similar performance with a HTTP protocol. I knew that you can gain
some performance by using a well-defined binary protocol in blocking mode,
but seeing this in action was quite amazing.

The only downside when using NexusDB components as a transport for RTC SDK
is that you won't be able to use "standard" RTC Clients to communicate with
RTC Servers on the NexusDB transport, nor have RTC Clients over a NexusDB
transport talking to a Web Server or a "standard" RTC Server, since NexusDB
components have a specific (binary) format for communication and pack
additional data into streams being sent/received.

IOW, you will need a NexusDB Client to talk to a NexusDB Server.

But, to compensate for this, in case someone wants to use NexusDB transports
inside a LAN, but still make the same application accessible from the
internet by using the HTTP protocol, I will add a new component to the RTC
SDK, which will make it possible to link your rtcDataProvider and
rtcServerModule components (implementing the server-side functionality) to
more than one Server component (rtcServerSplitter?). That way, you will have
the same functionality accessible through more than one channel (HTTP,
HTTPS, NexusDB, etc) by linking your application code to multiple server
components.

Best Regards,
Danijel Tkalcec, Team RTC
http://www.realthinclient.org


.

Relevant Pages

  • ANN: NexusDB AWE Server Trial now available
    ... NexusDB Server AWE edition brings you the possibilities of 64-bit ... The NexusDB AWE edition is a normal win-32 executable that runs on any ... AWE edition on a 16 gigabytes RAM, 8 core server, and dedicate 12 ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Looking for database that is easy to install
    ... NexusDB will fit your needs here. ... Copy the server exe file onto the designated file server. ... > the single file database and only having to ensure ADO is installed on the ... > acting as a server or their own client machine and have it install the ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Using FB in embedded mode? (Re: Embedded into EXE DB systems.)
    ... > I gather from this ng that there are some units floating around that make ... > it sounds more complex than in NexusDB where you just drop the appropriate ... > My initial feeling was that FB (along with NexusDB, MS SQL Server, etc) ... > architected for embedded apps. ...
    (borland.public.delphi.thirdpartytools.general)
  • Using FB in embedded mode? (Re: Embedded into EXE DB systems.)
    ... My initial feeling was that FB (along with NexusDB, MS SQL Server, etc) ... architected for embedded apps. ... >> If you mean an embeded Database, ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: The best small/medium database...?
    ... Eugene Mayevski wrote: ... > Yes, so great, that adding SSL layer is just impossible ... ... way to implement SSL/TLS layer over NexusDB transports. ...
    (borland.public.delphi.thirdpartytools.general)