Thanks Mone. A few follow-up questions if you don't mind:

1. I picture tables as being created on the client side and sent
to the server for it to use when processing update events. Is
this correct?

2. Is the monotable approach scalable? For my use case I hope to
have hundreds of thousands of concurrent users, with an average of
perhaps 10 monotables per user. Of course I recognize that I may
have to spread the users over two or more Lightstreamer instances,
but I am trying to get a sense of how using monotables will affect
scalability.

2. Is it ok to share a schema across mono-tables?

3. I see that your code examples make heavy use of double brace
initialization (!) for table info and table listener objects. Is
this just a matter of coding taste, or is double brace
initialization better for these cases than other styles of
initializing objects?

4. I have not been able to understand some aspects of command mode
as it is described in the General Concepts document (and I haven't
started experimenting with it yet - as I mentioned, I am new to
Lightstreamer). Two sections of the description of command mode
in particular puzzle me:

a) "The itemEvents are interpreted as commands that indicate how
to progressively modify a table or a list."

As far as I know, Lightstreamer exposes a table construct but no
list construct. Is the documentation saying that command events
can modify the contents of the server-side table data structure,
or is it saying "If you are maintaining your own
(non-Lightstreamer) table or list in your client code, here is a
convenient way to trigger changes to it."?

b) "Notice that a field of the schema in a COMMAND subscription
could contain the itemName of a
different item. This way, it is possible to perform a multi-level
push, where a change in the
first-level item can provoke subscription or unsubscription to
different second-level items (and
so on)."

Does this mean that a command event can cause an item to be added
to (or removed from) a Lightstreamer table, and that the added
(removed) item will be automatically subscribed (unsubscribed)?

-Dan