1. 02 12月, 2011 1 次提交
  2. 29 7月, 2011 1 次提交
  3. 18 7月, 2011 5 次提交
  4. 15 7月, 2011 1 次提交
  5. 19 4月, 2011 1 次提交
  6. 18 3月, 2011 2 次提交
  7. 16 3月, 2011 1 次提交
  8. 12 1月, 2011 2 次提交
    • J
      rpc: allow xprt_class->setup to return a preexisting xprt · f0418aa4
      J. Bruce Fields 提交于
      This allows us to reuse the xprt associated with a server connection if
      one has already been set up.
      Signed-off-by: NJ. Bruce Fields <bfields@redhat.com>
      f0418aa4
    • J
      rpc: keep backchannel xprt as long as server connection · 99de8ea9
      J. Bruce Fields 提交于
      Multiple backchannels can share the same tcp connection; from rfc 5661 section
      2.10.3.1:
      
      	A connection's association with a session is not exclusive.  A
      	connection associated with the channel(s) of one session may be
      	simultaneously associated with the channel(s) of other sessions
      	including sessions associated with other client IDs.
      
      However, multiple backchannels share a connection, they must all share
      the same xid stream (hence the same rpc_xprt); the only way we have to
      match replies with calls at the rpc layer is using the xid.
      
      So, keep the rpc_xprt around as long as the connection lasts, in case
      we're asked to use the connection as a backchannel again.
      
      Requests to create new backchannel clients over a given server
      connection should results in creating new clients that reuse the
      existing rpc_xprt.
      
      But to start, just reject attempts to associate multiple rpc_xprt's with
      the same underlying bc_xprt.
      Signed-off-by: NJ. Bruce Fields <bfields@redhat.com>
      99de8ea9
  9. 19 10月, 2010 2 次提交
  10. 02 10月, 2010 3 次提交
  11. 04 8月, 2010 2 次提交
  12. 25 5月, 2010 1 次提交
  13. 18 5月, 2010 1 次提交
  14. 15 5月, 2010 6 次提交
  15. 21 4月, 2010 1 次提交
  16. 22 3月, 2010 1 次提交
  17. 03 12月, 2009 1 次提交
  18. 12 9月, 2009 1 次提交
  19. 18 6月, 2009 4 次提交
  20. 03 5月, 2009 1 次提交
  21. 12 3月, 2009 2 次提交