I have an architecture divided in two part:
The problem: How can I do to redirect some SOAP call (depending on the soapaction) from the master to one of the others (randomly).
My solution: I have an http handler that choose if we redirect the request or not, if yes it write the full incoming request in a new HttpRequest and write the incoming response in the Response. And this works well in production, but I don't like it, mainly because it's an in-house solution and I don't think we are the best at this kind of job, and my solution doesn't support soap 1.2.
System: Windows server 2005, .net 2.0
Is there any better solution? already build and debugged?
thanks
This already is a good solution, isn't it?
Redirecting incoming requests to different physical machines is often done on network level, eg round-robin DNS for load distribution etc. However, I don't think you can apply that in this scenario.
If if works, don't fix it.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.