i'm not sure how your app currently handle sessions but you can mitigate the problem by storing the session outside of the web server and store it on the database or memcached servers, e.g. PHP's session_set_save_handler().
however, zero interruption is not guaranteed since large websites even experience such. the key is on how your app handles the problem via error handling (w/ AJAX). On Tue, Apr 15, 2008 at 6:56 AM, Jagi Sarcilla <[EMAIL PROTECTED]> wrote: > [....] > > *web1 and web2 apache webserver > app1 and app2 jboss app server > **db1 and db2 mysql db server* > > > i need a failover solutions for web, app and db1, but when the failures > occur on web, it must not interrupt or cut the session. > seamless process, you will not experience disconnections or interruptions. > > any idea, solutions and suggestions on this type of requirements. > > [....]
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
