Products

Price/Order

Support

Partners

Testimonials

Test Results

About us

Contact
 TRtcMessageClient and TRtcMessageServer Components.
Bottom
 
Total posts: 5
 Author TRtcMessageClient and TRtcMessageServer Components.
Steve Gill

05.07.2006 02:57:10
Registered user
Hi Danijel,

I'm very interested in the new TRtcMessageClient and TRtcMessageServer components.  Forgive my ignorance but what do they actually do?  Is it possible to use them as a basis for a chat type application?  Is there any information available on how they work?  Do they require a 3rd party transport mechanism?

Thanks.

Regards,

Steve
Danijel Tkalcec [RTC]

05.07.2006 05:42:42
Registered user
Hi Steve,

rtcMessageClient and rtcMessageServer are message-based client and server components doing the same thing rtcHttpClient and rtcHttpServer components do, but with the difference that they are using a direct link (link rtcMessageClients to a MessageServer through the Server property on rtcMessageClient) or third-party transports (like NexusDB communications framework) to communicate.

If you have NexusDB components and would like to tunnel all your RTC communication over NexusDB connections, you would use rtcMessageClient and rtcMessageServer components instead of rtcHttpClient/Server components.

So, to answer your question ... you can use rtcMessageClient and rtcMessageServer components to write a chat type application, the same way you can use rtcHttpClient and rtcHttpServer for this task (using RTC remote functions).

Best Regards,
Danijel Tkalce
Steve Gill

07.07.2006 04:06:48
Registered user
Thanks Danijel.  So besides the ability to use plugin transport mechanisms, is there any advantage in using rtcMessageClient and rtcMessageServer instead of the rtcHttpClient and rtcHttpServer?

Regards,

Steve
Danijel Tkalcec [RTC]

07.07.2006 10:57:34
Registered user
Except the fact that you can use those components to compile client and server in one executable without any transports in-between, there is no other advantage. Those are "only" connection components, just like TRtcHttpClient and TRtcHttpServer, but they use plugin transports instead of built-in TCP/IP.

If you are asking for pointers on writing rich chat-type applications, you may want to take a look at the RTC Messanger Client/Server. To write a web-based chat, it takes some JavaScript and HTML knowledge combined with a server-side "message dispatcher", like the one used in the RTC Message Server.

PS. What kind of advantage did you have in mind?

Best Regards,
Danijel Tkalcec
Steve Gill

08.07.2006 04:07:04
Registered user
Thanks Danijel.  Nothing comes to mind in the way of advantages.  I am starting to write a chat program using TRtcHttpClient and TRtcHttpServer.  When I heard about rtcMessageClient and rtcMessageServer, I thought I'd better find out more about them before going too far with TRtcHttpClient and TRtcHttpServer, in case the new components included something that would make things easier.

Regards,

Steve