Hi Jarl.
Revisiting this issue after quite a while. One possible explanation for the behavior we were seeing is that it's another facet of the inability of RCF to have multiple outstanding requests on a connection. I'm not yet sure if that is the case, but it's a theory.
Is there any update on that particular feature request?
Thanks.
Dave
Exception attempting to use Http Tunneling
Re: Exception attempting to use Http Tunneling
Hi Dave,
At this point it doesn't look like we can implement multiple outstanding requests on a single connection, because it would break the HTTP tunneling feature. The HTTP protocol does not allow multiple outstanding requests in general (there is the 'pipelining' hack but it's pretty limited and not suitable for remote calls), and I'm not keen on implementing features in RCF that will break when a HTTP tunnel is involved.
It could be made to work with HTTP/2, but that's yet more work that I can't commit to at the moment.
At this point it doesn't look like we can implement multiple outstanding requests on a single connection, because it would break the HTTP tunneling feature. The HTTP protocol does not allow multiple outstanding requests in general (there is the 'pipelining' hack but it's pretty limited and not suitable for remote calls), and I'm not keen on implementing features in RCF that will break when a HTTP tunnel is involved.
It could be made to work with HTTP/2, but that's yet more work that I can't commit to at the moment.