Aren't the transports and protocols plugins to the
remoting abstraction? They don't have to live in
the remoting module.
yes, you're right. however, we've included some standard transports, detectors in remoting so they're available out-of-the-box. i would imagine as it grows, each component might have different transports, etc. to handle their component specific remoting needs.
I personally think it should be kept separate, but I am biased because I may want to use for something completely unrelated to JBoss. I wanted to see the code first though. Can't seem to find the remoting package in org/jboss directly like the JBossRemoting.pdf says though.
I personally have been trying to figure out a way to separate my api and my transport protocol for some time and haven't yet run into anything I like, nor come up with anything I like either. There tends to be so much trouble especially dealing with cleaning up listeners when a particular client goes away. It is a very interesting problem though.