You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@river.apache.org by "Thomas Vinod Johnson (JIRA)" <ji...@apache.org> on 2007/07/27 16:37:18 UTC

[jira] Created: (RIVER-103) (perf?) reduce wrapping in net.jini.jeri.connection.(Server)ConnectionManager

(perf?) reduce wrapping in net.jini.jeri.connection.(Server)ConnectionManager
-----------------------------------------------------------------------------

                 Key: RIVER-103
                 URL: https://issues.apache.org/jira/browse/RIVER-103
             Project: River
          Issue Type: Improvement
          Components: net_jini_jeri
    Affects Versions: jtsk_2.0
            Reporter: Thomas Vinod Johnson
            Priority: Minor


Bugtraq ID [4856370|http://bugs.sun.com/bugdatabase/view_bug.do?bug_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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.