Sunday, September 21, 2014, 6:37:51 PM, you wrote: > So, I guess I don't understand why TSVConnTunnelToAddr is not useful? Could > you elaborate?
I, personally, just don't like it. I think the general use case will be to simply tunnel without changing the server address, and since you can't overload in the C interface the client will have to pass a completely useless address every time. Much better, IMHO, to have a separate call to set the target address in the odd cases where that's useful. >> tsapi void TSVConnReenable(TSVConn); >> It was not clear to me, where the event parameter should be sent. > In the absence of an event parameter, what's the right way to abort the VC > with an error? How can an error be reported at all? The logging code requires an HttpSM instance and we don't have one of those. Internally, what continuation would receive the event? The netVC? Also, I thought it was your suggestion that we use TSVConnAbort() for this purpose, which takes an error argument. But I would recommend that as the mechanism to abort the VC with an error.
