If I did something like that, then the Flex application would effectively cause the session to never expire. What I'm looking for is a way to integrate a Flex application with sessions such that user interaction in the application keeps the session alive. That said, I'd also prefer to not make calls specific to maintaining the session, such as calling PHP and an alternate web service in the same domain. If that is required, I'd be better off calling PHP and handling the service on the PHP side.
When a session is created, the session ID is provided with all calls back to that domain, correct? So, is there a way to check the status of a session from a web service and keep it alive? In other words, can I access the session information stored by PHP by an external source? --- In [email protected], Fotis Chatzinikos <fotis.chatzini...@...> wrote: > > if your session expires every lets say 30 minutes, make the client hit a > simple page that does nothing every lets say 25 minutes- > make sure that this is not cached by appending a timestamp in the url > > On Wed, Mar 11, 2009 at 11:23 PM, wubac1 <wub...@...> wrote: > > > I'm hoping someone can shed some light on a design issue I'm facing. If > > I have a sign in form external to Flex, but it controls access to the Flex > > application, what are the best practices for maintaining the session when > > the user is interacting with the Flex application? I can provide the Flex > > application the session ID, but what do I do with it to ensure that the > > session does not expire while a user is working in the application? I'm > > using web services, so I wonder if I should be checking the session at the > > point. For example, if I have a PHP-based website hosting an adobe Flex > > application, with a PHP sign in form, what should I be doing with regard to > > Flex, if the application uses web services outside of PHP (such as gSOAP, > > Axis2/C, or one of the various Java options)? > > > > I can see how this would work if the Flex application used PHP as the > > back-end, since all communication would go though a single source that > > manages the session. However, what I don't understand and have found little > > with regard to answers on the subject, is how to integrate a Flex > > application that utilizes an alternate back-end from the hosting website. > > I'm my case, the alternate back-end is in the same domain, so I suspect > > there should be a way to share the session information between PHP and other > > services such as web services in gSOAP. Has anyone faced this design issue? > > Thoughts on an appropriate solution? Is this approach worth the trouble or > > should I be calling PHP that then routes requests to the web services (or > > implements the service)? > > > > A visualization: > > > > PHP login --> PHP back-end --> database > > | > > | > > Flex <-- (PHP returns page with Flex Application) > > --> web service (non-PHP; but same domain) --> database > > > > > > > > > > -- > Fotis Chatzinikos, Ph.D. > Founder, > Phinnovation > fotis.chatzini...@..., >
