You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mechanics of using leasing from a requester's perspective are somewhat convoluted. You have to manually deal with waiting for leases to be acquired initially, and then separately track new leases, and finally connecting that into further requests. In addition a server side requester cannot even do that because it has no way to obtain a leases receiver for the current connection.
The idea is to try and encapsulate the acquiring of a lease in an RSocketProxy or perhaps build it into RSocketRequester such that an application can make requests as usual but internally that would involve acquiring a lease. This would make it straight forward to make requests with leases from both sides.
The text was updated successfully, but these errors were encountered:
The mechanics of using leasing from a requester's perspective are somewhat convoluted. You have to manually deal with waiting for leases to be acquired initially, and then separately track new leases, and finally connecting that into further requests. In addition a server side requester cannot even do that because it has no way to obtain a leases receiver for the current connection.
The idea is to try and encapsulate the acquiring of a lease in an
RSocketProxy
or perhaps build it intoRSocketRequester
such that an application can make requests as usual but internally that would involve acquiring a lease. This would make it straight forward to make requests with leases from both sides.The text was updated successfully, but these errors were encountered: