Questions about The optional Real-Time Messaging (RTM) module

[SchlauKunde]

1. CHANNELS: I have not found any in-depth information about channels, e.g. how to create them ...

2. DATA which can be sent by messaging:
- The RTM docs say the following about the "send" method: Messaging.send(channels, data): Send any data (primitive type, or compound data structure) ...

Now the general statement about data exchange capabilities is the following (on the SmartClient Server Summary page):

		Automatic Bi-directional Java < - > JavaScript serialization and translation

		Provides a powerful, type-safe data transmission mechanism for moving data between a Java
		server and the browser. 

		Any Java objects, including Java Beans, POJOs, Java Collections, XML DOMs and all Java
		primitives, with any level of nesting, can be automatically serialized and delivered as
		JavaScript Objects to the SmartClient client-side components. 

		JavaScript Objects existing in the browser can likewise be automatically transmitted to a
		Java Server and translated to Java Objects, with any level of nesting and automatic
		preservation of primitive types.

Does this general statement hold for the data handled with SmartClient's messaging, too ? That is can one for example push an arbitrary Java object data structure to the browser where it is automatically converted to its corresponding JavaScript object data structure ? That would be a quite powerful realtime data exchange engine then ...

[Isomorphic]

1. Channels do not need to be explicitly created. You start listening by channelId, and if someone addresses something to that channelId, you receive it.

2. Yes, data structures passes through messaging are converted to JavaScript objects via the JSTranslater, the same mechanism underlying the RPC communications.

[SchlauKunde]

This sounds quite exciting to me :-) ! Because it sounds like the SmartClient RTM offers powerful messaging: Channels must NOT be defined statically in advance somewhere, but can be defined dynamically on the fly. Is that correct ? And is there a limit on the number of channels the RTM can handle concurrently ?

[Isomorphic]

Only hardware limits, really.