A few questions about mod_fastcgi and session affinity

[email protected]
Newsgroups gmane.comp.web.fastcgi.devel
Message-ID <OF810F4894.A5F20459-ON87256EFD.005A1540-87256EFD.0059E213@mmm.com>



I've got a few questions about mod_fastcgi and session affinity.  I might
preface this by saying that I downloaded the
archived mailing list and read everything I could find about session
affinity and I am still a bit confused.  I am building
a web application that will use Apache on Linux.  The application itself is
persistent and long-running.  The web server
must be able to tie one client browser to one running persistent
application that will remain active and connected for
hours though it will probably only run for a few seconds at any one client
access.  The state information must remain
between accesses, however.

In reviewing the mailing list there seems to have been a bit of controversy
as to whether the session affinity patch should
be added to the FastCGI codebase or not.  The released version of
mod_fastcgi does not seem to contain the patch.
Here are my questions:

1) In reviewing CVS for mod_fastcgi I see there is a "sa_branch" that was
built several months back.  Does this branch
contain the latest and complete session affinity patch?  Also, can this
branch be down-loaded and built as it is?  Has
anyone tested this branch?

2) I noticed in the logs that there was some discussion of removing
"exclusive mode" from session affinity.  Was this removed?
Given that I must tie one client browser to one running applications for a
potentially very long time, I think I will need this
exclusive ability.

3) Finally, could you tell me what the current status of mod_fastcgi is.
Will the "sa_branch" every be released?  What is the
future of the package?

Thanks anyone for helping me understand this system better!
Larry Cousin

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.