Hi Ron, I have implemented a few projects using CGI::Application and using frames. The thing to look out for is to not load both frames at the same time, then you tend to generate 2 different sessions. Try loading the left frame first and then the right frame, kind of a staged loading, then there should not be the problem with the two sessions. I hope this helps, it is something I have stumbled across.
You could also have the frameset be generated by CGI::Application, but still be carefull when load two frames almost at the same time, session data could get lost and you could get problems with session locking. Best regards Patrick W. Fraley Am Mo, den 05.07.2004 schrieb Ron Savage um 06:11: > Hi Folks > > I have a setup using CGI::App which starts like this in the HTML: > <frame name="left" src="http://127.0.0.1/cgi-bin/left.cgi";> > <frame name="right" src="http://127.0.0.1/cgi-bin/right.cgi";> > > The frames have worked out superbly, despite the fact I normally > abstain from such practices... If a solution to the problem > below requires abandoning frames, then so be it, but I won't > abandon them lightly. > > The 2 scripts are the same, just differing in the PARAMS: > My::Application -> new(PARAMS => {target => 'left'}) -> run(); > My::Application -> new(PARAMS => {target => 'right'}) -> run(); > > The problem is that each script creates its own CGI::Session session, > so that when a user operating in the right frame sets options, > the session in the left frame is unaware of the changed options. > > How do I let the left session become aware of the right session, > given the constaints: > o The code must run identically under Linux and Windows, so I'm > reluctant to adopt a solution requiring fork; > o The code is being rolled out to 13,000 desktops, which influences > how many people could theoretically start up the scripts at > more-or-less the same time. See below for a discussion of client IP > addresses, which would otherwise be pressed in to use here. > > The reason IP addresses may not be enough to distinguish clients, > is that the last time I tested IP addresses via Apache's log (in > a different environment), all requests were logged with the (same) > router's IP address, rather than the client's IP address. -- *************************************** COMsulting Gerhard Faehling GmbH Patrick W. Fraley Oeverdieker Weg 6 23669 Timmendorfer Strand Tel: 04503 / 88 12 45 Fax: 04503 / 88 10 18 E-Mail: [EMAIL PROTECTED] Internet: www.comsulting.de *************************************** --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
