Joe,
>
> With constant flow on this list about session problems,
Yes (but this include also questions about cookies in general)
> have you considered
> just having Embperl handle everything for sessions? I'm not even sure if
> this is possible since sessions are out of my experience, but my ONLY
> problem with Embperl were sessions and how difficult they were to get up
and
> running. Additionally, I have had many "weird" experiences even when I
> think the sessions are working correctly. I have also had the problem of
> other users seeing my session after I login. This is very scary and does
> not bode well for a robust scripting language. I believe PHP does its own
> session handling, why not do something similiar and get rid of reliance on
> perl modules like Apache::Session.
>
I don't think that we gain anything when integrate session directly into
Embperl, but we loose the time that it would take to implement for doing
other improvements. I think we will run into the same problems, if Embperl
would offer the same possibilities. Apache::Session is a storage module for
sessions and it does it job well. There are a lot of thinks that it didn't
do and that are things we should take time to implement them in Embperl.
That's what I currently try to do.
I see two problem with session setup:
Documentation is not at one place: Parts are in the Embperl docs, parts are
in the Apache::Session docs. I have tried to improve the docs in Embperl, so
they show the way and where to find more information. It would be good to
extent the FAQ with Session stuff, but currently I don't have the time to do
so, but everybody how likes to contribute anything is welcome and I will
include it in the FAQ.
Apache::Session has many possibility: It maybe confusing for new people. I
have thougth about how to add default values for the session configuration,
but I can't think of anything that would work everywhere. I think the
current two parameters that have to be setup are the minimum. If anybody has
a better idea let me know.
For your concret problem there are many possible reasons:
(I don't have in mind every detail from our preivous mail exchange, so maybe
I repeat something)
1.) a gobal variable holding it's content (outside a Embperl, Embperl only
cleansup variable which are declared inside a Embperl page)
2.) Cooke mixup of differnent machines, like Cliff pointed out. This can be
prevented by either setting COOKIE_DOMAIN correct, or using differntr cookie
names
3.) If you don't have set cookie path, then the cookies will only send back
to the directory you first received them and below (same for different
hosts/ports). So you will loose your session, if you request the "wrong"
directory.
4.) It maybe a locking problem, but I am not sure if it really is. I would
consider the other possibility more likely. If it comes down to a locking
problem, then it looks to me that it is an error of Embperl and have to be
fixed, but I have review the code for the recent changes and didn't see any
bug here.
Dumping out %udat for debugging is a good idea, so we can (maybe) see better
where the content disapears/changes. For example it would interessting if
you get always the same session id or if the session id disapears in the
http headers (use dbgHeadersIn to view in and outgoing headers in the
logfile)
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925151
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
