Managing non http requests
I'm checking the feasibility of building a 'message server' based on Tomcat that will receive messages (xml or other format) from clients, route them to a backend system and send the response. 1. There maybe situations that the application response to the http request should be sent to a different url or maybe even using non http protocol (asynchronous mode). How should I handle this case so that the client will receive an immediate response and disconnect while the thread continues to process the request? 2. I will also accept request from MQ and other non http channels. Is there a way to enjoy Tomact services like thread pooling for those requests? Should I package them in http and resend to the web server? Thanks Zvi Bruckner
RE: Managing non http requests
I'm checking the feasibility of building a 'message server' based on Tomcat that will receive messages (xml or other format) from clients, route them to a backend system and send the response. 1. There maybe situations that the application response to the http request should be sent to a different url or maybe even using non http protocol (asynchronous mode). How should I handle this case so that the client will receive an immediate response and disconnect while the thread continues to process the request? 2. I will also accept request from MQ and other non http channels. Is there a way to enjoy Tomact services like thread pooling for those requests? Should I package them in http and resend to the web server? If I am following you correctly a RequestInterceptor could be used for this. --- Michael Wentzel Software Developer Software As We Think - http://www.aswethink.com
