Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
jtsk_2.0
-
None
-
None
-
4856370
Description
Bugtraq ID 4856370
Now that the connection manager implementations of the net.jini.jeri.connection package are the only users of the com.sun.jini.jeri.internal.mux API, they could be better integrated. ConnectionManager and ServerConnectionManager currently do a lot of wrapping around MuxClient and MuxServer and the OuboundRequest and InboundRequest instances they provide, but that could be unnecessary if the com.sun.jini.jeri.internal.mux API was more directly an implementation of the net.jini.jeri.connection APIs. Reducing this wrapping might provide a small (although probably negligble) performance improvement for (Server)ConnectionManager-based transport providers. It would also make the implementation a bit cleaner.
Attachments
Issue Links
- is related to
-
RIVER-318 JERI Performance Issues
- Open