Thursday, July 5, 2018

WSE 3.0 client - is there a way to open HTTPS tunnel before actually sending the SOAP message?

Hi there. Forgive me if it's something stupidly simple but I'm still relatively new to .NET and Google did not tell me anything about this.

So, I'm working on a client for a webservice. It's WSE 3.0 because I was basing this off a previous app, the service is WSE 3.0 based as well and there's a lot of custom security headers so porting this to WCF would be a pain, I don't have a lot of time to do this either. This app however is quite time critical and I'm wondering about ways to shave some off. The biggest one I can see is the HTTPS tunnel - each time I'm sending a SOAP message, on the first one I can see in Fiddler a HTTPS tunnel needs to open, eating a few seconds of time, the next ones from the same client object go fast.

In very simple terms, the app is supposed to send messages precisely at predefined times, doing it as fast as possible is very important. I was wondering whether is there a way to just open the tunnel a few seconds before the planned time, then send the message on it? Sending a dummy one before the time to open the tunnel isn't a good solution due to how API would treat them unfortunately. The client is Web.Services3.WebServicesClientProtocol if it helps.

Thanks a ton!

WSE 3.0 client - is there a way to open HTTPS tunnel before actually sending the SOAP message? Click here
  • Blogger Comment
  • Facebook Comment

0 comments:

Post a Comment

The webdev Team