Overview of RemObjects SDK Components (Delphi)
From RemObjects Software
This is a RemObjects SDK Components entry
Feel free to add your notes to this topic below.
| | |
|---|---|
            
Channel Components | These are the channel components, that are used on the client side to establish a communication to the server. Different types of channels are available (indicated by the overlay icon in the bottom corner), and for some of the types, different implementations are provided (indicated by letters in the top left corner, for Indy, or Synapse). Channels and Servers of same type are wire-compatible. Please refer to the Channels topic for a detailed comparison of the different channels and servers. |
           
Server Components (aka Server Channel Components) | These are the server components, which are used on the server side to make the application accessible to clients. As with channels, different types are available (indicated by the overlay icon in the bottom corner), and for some of the types, different implementations are provided (again, indicated by letters in the top left corner, for Indy, BPDX or Synapse). Channels and Servers of same type are wire-compatible. Please refer to the Channels topic for a detailed comparison of the different channels and servers. |
   
Message Components | These are the message components, used to encode the requests and responses that are passed between client and server. The message format is indicated by a small letter in the upper right corner, for BinMessage, PostMessage, SOAP and XMLRPC. Please refer to the Messages topic for a detailed comparison of the different message formats. |
   
Session Manager Components | Session Managers are used to persist per-client information, so called session data, between calls. Different types of Session Managers are provided out of the box to suit individual needs; please refer to the Session Management help topic for a more detailed discussion on sessions and the different session manager components. |
 
Event Repository Components | Event Repositories build on top of the session manages to store and process callback events that will be sent back to individual clients.Please refer to the upcoming Event Sinks and Server Callbacks topic for more details. |
Event Receiver Component | Event Receivers are used on the client side to poll or actively receive callback event messages from a server, and initiate execution of the events. Please refer to the upcoming Event Sinks and Server Callbacks topic for more details. |
 
Discovery Components | The Discovery Client and Server are special components that can be used to discover available servers on the local network, based on load or published services. |
Remote Service Component | The Remote Service component is used to represent the connection to a remote service - both the channel and message component as well as the name of the service. See the TRORemoteService help topic for more details. |
Dynamic Request Component | The Dynamic Request component can be used to construct requests to a server dynamically a runtime, without the method information or a proxy object being available at compile time.See the TRODynamicRequest help topic for more details. |
"Powered By" Button | Let the world know that you use RemObjects SDK by adding this button to your application's About Box. The button provides two views, featuring the client and the server icon. Clicking the button will launch the RemObjects Software website ([1]) in the user's web browser. |
See Also
Product: RemObjects SDK
Current version: RemObjects SDK 'Vinci' (5.0)
Lists — Glossary — Features — How To — Components — Tools — Samples — Articles — Architecture — Issues
