Re: post redirect get to the same tomcat instance in a tomcat cluster ?
On 12 Jun 2012, at 18:17, Albert Kam moonblade.w...@gmail.com wrote: Hi all ! Is it possible to do POST submit to the tomcat-A, redirect happens, and then GET to the same tomcat-A again in a tomcat cluster ? And, in hope to make things easier, all the tomcat servers in the cluster are stateless wihout any sessions You contradict this statement below by saying it does use s This needs arise because each tomcat servers will have it's own spring context (a kind of state, but not a per-user-session), and i am making use of flash attribute feature detailed in here : http://static.springsource.org/spring/docs/3.1.x/spring-framework-reference/html/mvc.html#mvc-flash-attributes Here are the relevant quotes from the page : Flash attributes provide a way for one request to store attributes intended for use in another. This is most commonly needed when redirecting — for example, the Post/Redirect/Get pattern. Flash attributes are saved temporarily before the redirect (typically in the session) to be made available to the request after the redirect and removed immediately. Flash attribute support is always on and does not need to enabled explicitly although if not used, it never causes HTTP session creation. On each request there is an input FlashMap with attributes passed from a previous request (if any) and an output FlashMap with attributes to save for a subsequent request. Both FlashMap instances are accessible from anywhere in Spring MVC through static methods in RequestContextUtils. -- Do not pursue the past. Do not lose yourself in the future. The past no longer is. The future has not yet come. Looking deeply at life as it is in the very here and now, the practitioner dwells in stability and freedom. (Thich Nhat Hanh) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: post redirect get to the same tomcat instance in a tomcat cluster ?
On 13/06/2012 13:13, Pid * wrote: On 12 Jun 2012, at 18:17, Albert Kam moonblade.w...@gmail.com wrote: Hi all ! Is it possible to do POST submit to the tomcat-A, redirect happens, and then GET to the same tomcat-A again in a tomcat cluster ? And, in hope to make things easier, all the tomcat servers in the cluster are stateless wihout any sessions You contradict this statement below by saying it does use s (Oops. Fat finger + touch screen...) You contradict this statement below by saying it does use sessions, below. Just because you are not directly using a session, it does not mean that a framework isn't doing so behind the scenes. If there's no need to replicate sessions, you can still use the sticky-session mechanism to pin a session to a node. See server.xml, Engine.jvmRoute in the docs. p This needs arise because each tomcat servers will have it's own spring context (a kind of state, but not a per-user-session), and i am making use of flash attribute feature detailed in here : http://static.springsource.org/spring/docs/3.1.x/spring-framework-reference/html/mvc.html#mvc-flash-attributes Here are the relevant quotes from the page : Flash attributes provide a way for one request to store attributes intended for use in another. This is most commonly needed when redirecting — for example, the Post/Redirect/Get pattern. Flash attributes are saved temporarily before the redirect (typically in the session) to be made available to the request after the redirect and removed immediately. Flash attribute support is always on and does not need to enabled explicitly although if not used, it never causes HTTP session creation. On each request there is an input FlashMap with attributes passed from a previous request (if any) and an output FlashMap with attributes to save for a subsequent request. Both FlashMap instances are accessible from anywhere in Spring MVC through static methods in RequestContextUtils. -- Do not pursue the past. Do not lose yourself in the future. The past no longer is. The future has not yet come. Looking deeply at life as it is in the very here and now, the practitioner dwells in stability and freedom. (Thich Nhat Hanh) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- [key:62590808] signature.asc Description: OpenPGP digital signature
Re: post redirect get to the same tomcat instance in a tomcat cluster ?
Oops, i really misread the documentation, thinking it will never use session to provide that feature. Thank you for the pointers ! On Wed, Jun 13, 2012 at 7:23 PM, Pid p...@pidster.com wrote: On 13/06/2012 13:13, Pid * wrote: On 12 Jun 2012, at 18:17, Albert Kam moonblade.w...@gmail.com wrote: Hi all ! Is it possible to do POST submit to the tomcat-A, redirect happens, and then GET to the same tomcat-A again in a tomcat cluster ? And, in hope to make things easier, all the tomcat servers in the cluster are stateless wihout any sessions You contradict this statement below by saying it does use s (Oops. Fat finger + touch screen...) You contradict this statement below by saying it does use sessions, below. Just because you are not directly using a session, it does not mean that a framework isn't doing so behind the scenes. If there's no need to replicate sessions, you can still use the sticky-session mechanism to pin a session to a node. See server.xml, Engine.jvmRoute in the docs. p This needs arise because each tomcat servers will have it's own spring context (a kind of state, but not a per-user-session), and i am making use of flash attribute feature detailed in here : http://static.springsource.org/spring/docs/3.1.x/spring-framework-reference/html/mvc.html#mvc-flash-attributes Here are the relevant quotes from the page : Flash attributes provide a way for one request to store attributes intended for use in another. This is most commonly needed when redirecting — for example, the Post/Redirect/Get pattern. Flash attributes are saved temporarily before the redirect (typically in the session) to be made available to the request after the redirect and removed immediately. Flash attribute support is always on and does not need to enabled explicitly although if not used, it never causes HTTP session creation. On each request there is an input FlashMap with attributes passed from a previous request (if any) and an output FlashMap with attributes to save for a subsequent request. Both FlashMap instances are accessible from anywhere in Spring MVC through static methods in RequestContextUtils. -- Do not pursue the past. Do not lose yourself in the future. The past no longer is. The future has not yet come. Looking deeply at life as it is in the very here and now, the practitioner dwells in stability and freedom. (Thich Nhat Hanh) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- [key:62590808] -- Do not pursue the past. Do not lose yourself in the future. The past no longer is. The future has not yet come. Looking deeply at life as it is in the very here and now, the practitioner dwells in stability and freedom. (Thich Nhat Hanh) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
post redirect get to the same tomcat instance in a tomcat cluster ?
Hi all ! Is it possible to do POST submit to the tomcat-A, redirect happens, and then GET to the same tomcat-A again in a tomcat cluster ? And, in hope to make things easier, all the tomcat servers in the cluster are stateless wihout any sessions This needs arise because each tomcat servers will have it's own spring context (a kind of state, but not a per-user-session), and i am making use of flash attribute feature detailed in here : http://static.springsource.org/spring/docs/3.1.x/spring-framework-reference/html/mvc.html#mvc-flash-attributes Here are the relevant quotes from the page : Flash attributes provide a way for one request to store attributes intended for use in another. This is most commonly needed when redirecting — for example, the Post/Redirect/Get pattern. Flash attributes are saved temporarily before the redirect (typically in the session) to be made available to the request after the redirect and removed immediately. Flash attribute support is always on and does not need to enabled explicitly although if not used, it never causes HTTP session creation. On each request there is an input FlashMap with attributes passed from a previous request (if any) and an output FlashMap with attributes to save for a subsequent request. Both FlashMap instances are accessible from anywhere in Spring MVC through static methods in RequestContextUtils. -- Do not pursue the past. Do not lose yourself in the future. The past no longer is. The future has not yet come. Looking deeply at life as it is in the very here and now, the practitioner dwells in stability and freedom. (Thich Nhat Hanh) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
