Using and Abusing Selectors... how far can I go?

Question

Hi,
I am currently looking at a system that consists of a 1000 clients that connect to BlazeDS. They exchange data with the server using messaging ( publish/subscribe ). Most of the data that goes to the clients corresponds to dynamic queries, for example:
Bind this label to the current value that results of evaluating this query: "select foo from x etc..."
( I am making this up to simplify, it is a bit more complicated than this, but it could very well be a simple SQL statement that is constantly evaluated ever 1 miniute or so ).
Now, here's the question. Currently, all clients create one or two consumers, and most of the responses for each of the queries come through those. So, I am basically multiplexing. Meaning that several "different" queries send their results through the same Consumer.
Internally, I do something like this ( again, pseudocode )
function processMessageResult( message )
  if ( message.query == query1 )
    updateBinding1(message.result)
  if ( message.query == query2 )
   updateBinding2(message.result)
etc..
Each client can easily have 400 active queries at a given moment and they are being re-evaluated constantly.
My first question is this:
What if, instead of multiplexing two Consumer on the client, I subscribe 400 different consumers and achieve the granularity via selectors?
Assuming the first one is not a redundant DON'T DO IT. The second question then is:
Can I listen to the subscriptions and inspect them, including defined selectors, on the server side?
I am thinking I can use the SQL 92 based selectors to build part of the "request" mechanism itself.
For example, a Consumer installs a filter: customerID=769
I can then say: Oh, someone wants me to run query A with this parameter.
I know I am pushing the limits here a bit. But the point is that the current logic is so complex that it makes sense to move it back and maybe even try to extend BlazeDS a bit. There is too much logic on the client side. That's not a good sign... and we will need other client techs to use this.
Thanks!
A

Answer 1

To put it in simple terms:
How will BlazeDS handle 400 subscriptions ( with complex selectors ) per client for 1000 clients?
Thats 400.000 consumers!
I haven't even tried. This is just  a crazy idea I want to explore.