Hi Scott, It depends on the MINA version you use. If you use 1.x, you can downcast the session into BroadcastIoSession and use write(Object, SocketAddress) method to send a message to a different port.
If you use 2.x, then you don't need to downcast. HTH, Krasnigor, Scott L (N-AST) wrote: > In my application, I am interfacing with multiple assets via UDP. I set > up a simple server that binds to a range of ports. When a message is > received from an asset, I use the Multiton package of classes to set up > single handler to process data received from the asset as well as send > data back to the asset. So if I am communicating with multiple assets, I > have one handler per asset to handle comms. If an asset goes offline, > the session is closed and the handler is cleared. An issue arose where > the folks on the asset side of things did not want to receive messages > on the same port that they are sending from. Is there a simple way to > handle their request without doing major redesign (adding client > handlers, changing from SingleSessionIoHandlers to regular IoHandlers > etc...). Sorry for babbling, long nights and no progress. Thanks for > your time. > > > > > > -- Trustin Lee - Principal Software Engineer, JBoss, Red Hat -- what we call human nature is actually human habit -- http://gleamynode.net/
signature.asc
Description: OpenPGP digital signature
