Generally speaking, we choose to model or wrap as MBean Services coarce grain entities.
In your case you seem to be creating some kind of Adapter for a socket-based protocol. Wrapping the socket into an MBean doesn't seem to offer much value. Wrapping a socket AND the protocol handling may make some sense, but it depends very much on the dynamic behaviour of your network protocol and your overall design. For example, does the network protocol involve just listening to events, translating them and do something with them? Do you want to have many message handlers per message? Do you want message processing to be synchronous or asynchronous. Do you need to send back replies to those clients? Answering those question will let you decide how best to design your MBean Services. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3857060#3857060 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3857060 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
