I'm working on http://jira.jboss.org/jira/browse/JBMESSAGING-207 which is related to configuring the Http remoting connector for messaging and currently it appears that a server peer is bound to a single connector. If I'm not mistaken this means that you have a single connection option per server configuration.
I believe the way MQ worked was that each invocation layer registered it's own ConnectionFactory in JNDI and it was upto the client to lookup the one that wanted to use.
I can think of serveral use cases where you might want to support serveral different connections options to the server. Especially when you have clients that are behind a firewall. You might also want external clients to use SSL but not for internal ones for performance reasons... etc
I spoke to Ovidiu and he feels it that it shouldn't be to hard to implement this.
Yes, it's actually pretty easy.
The difficult part is to get HTTP working. We might need to push this to 1.0.1. I'll take a look at it in the morning, though.