Re: [flexcoders]PHP and Flex questions
I too am very interested in this topic ! --- In flexcoders@yahoogroups.com, dorkie dork from dorktown [EMAIL PROTECTED] wrote: Could you give an example of how you do this? If this is secure it sounds much easier to handle. On 04 Apr 2007 10:12:22 -0700, Ray Horn [EMAIL PROTECTED] wrote: Rather than worry about the server session why not simply maintain the session state in the client since it is assume your client is running a SWF ala Flex. The fact that the client has accomplished a login could be handled by sending a specific token to the server as long as the token is some kind of UUID value that is known to be random yet non- sequential. I have coded this into a Flex Object that subclasses the HTTPService and once setup needs no further maintenance. In my specific case my app is always logged-in since it runs via an Intranet however my initial HTTPService call gets the user's metadata from the server and then I pass the user's ID back to the server on each HTTPService call but this is done transparently. Just a suggestion. I realize this may not be in keeping with the way most people might apprach this sort of problem. - Original Message From: dordea cosmin [EMAIL PROTECTED] To: flexcoders@yahoogroups.com Sent: Wednesday, April 4, 2007 1:27:44 AM Subject: Re: [flexcoders]PHP and Flex questions When a Flex application in a browser communicates with a php page for the first time a session is created. This is the same behavior as user receiving a PHP page in their browser. - true , but the session is created only if the php installed in your server is configured to auto start a session or you manually start the session in your scrip. - This session that is created last indefinitely with Flex applications because Flex keeps the connection open / session alive on the server. I am not sure if this is 100% true , but i believe by default , the http headers send Connection: Keep-Alive, so sessions remain alive. In my application it works okay, session doesn't expire while flex application runs. However, I believe if you send custom HTTP headers this behavior can be lost. - Flex keeps the connection alive by periodically pinging the server. same as above - Sessions will never timeout due to this behavior. same as above - When the user navigates away from the Flex application the session will timeout on the server. true , it will timeout in the time specified in your php.ini To manually timeout a session on the server call a page or function that executes this code session.destroy( ); -- not sure what the recommended method to clear the session on the server. - true , depending on your php session you will call the correct function to destroy the session Hope this helps. - Original Message From: dorkie dork from dorktown dorkiedorkfromdorkt [EMAIL PROTECTED] com To: [EMAIL PROTECTED] ups.com Sent: Tuesday, April 3, 2007 8:37:15 PM Subject: [flexcoders] PHP and Flex questions Can someone tell me if these statements are true or false and if false what is the correct answer? - When a Flex application in a browser communicates with a php page for the first time a session is created. This is the same behavior as user receiving a PHP page in their browser. - This session that is created last indefinitely with Flex applications because Flex keeps the connection open / session alive on the server. - Flex keeps the connection alive by periodically pinging the server. - Sessions will never timeout due to this behavior. - When the user navigates away from the Flex application the session will timeout on the server. - To manually timeout a session on the server call a page or function that executes this code session.destroy( ); -- not sure what the recommended method to clear the session on the server. Any answers will help even partial. -- 8:00? 8:25? 8:40? Find a flickhttp://tools.search.yahoo.com/shortcuts/? fr=oni_on_mail#newsin no time with theYahoo! Search movie showtime shortcut.http://tools.search.yahoo.com/shortcuts/? fr=oni_on_mail#news
Re: [flexcoders]PHP and Flex questions
Could you give an example of how you do this? If this is secure it sounds much easier to handle. On 04 Apr 2007 10:12:22 -0700, Ray Horn [EMAIL PROTECTED] wrote: Rather than worry about the server session why not simply maintain the session state in the client since it is assume your client is running a SWF ala Flex. The fact that the client has accomplished a login could be handled by sending a specific token to the server as long as the token is some kind of UUID value that is known to be random yet non-sequential. I have coded this into a Flex Object that subclasses the HTTPService and once setup needs no further maintenance. In my specific case my app is always logged-in since it runs via an Intranet however my initial HTTPService call gets the user's metadata from the server and then I pass the user's ID back to the server on each HTTPService call but this is done transparently. Just a suggestion. I realize this may not be in keeping with the way most people might apprach this sort of problem. - Original Message From: dordea cosmin [EMAIL PROTECTED] To: flexcoders@yahoogroups.com Sent: Wednesday, April 4, 2007 1:27:44 AM Subject: Re: [flexcoders]PHP and Flex questions When a Flex application in a browser communicates with a php page for the first time a session is created. This is the same behavior as user receiving a PHP page in their browser. - true , but the session is created only if the php installed in your server is configured to auto start a session or you manually start the session in your scrip. - This session that is created last indefinitely with Flex applications because Flex keeps the connection open / session alive on the server. I am not sure if this is 100% true , but i believe by default , the http headers send Connection: Keep-Alive, so sessions remain alive. In my application it works okay, session doesn't expire while flex application runs. However, I believe if you send custom HTTP headers this behavior can be lost. - Flex keeps the connection alive by periodically pinging the server. same as above - Sessions will never timeout due to this behavior. same as above - When the user navigates away from the Flex application the session will timeout on the server. true , it will timeout in the time specified in your php.ini To manually timeout a session on the server call a page or function that executes this code session.destroy( ); -- not sure what the recommended method to clear the session on the server. - true , depending on your php session you will call the correct function to destroy the session Hope this helps. - Original Message From: dorkie dork from dorktown dorkiedorkfromdorkt [EMAIL PROTECTED] com To: [EMAIL PROTECTED] ups.com Sent: Tuesday, April 3, 2007 8:37:15 PM Subject: [flexcoders] PHP and Flex questions Can someone tell me if these statements are true or false and if false what is the correct answer? - When a Flex application in a browser communicates with a php page for the first time a session is created. This is the same behavior as user receiving a PHP page in their browser. - This session that is created last indefinitely with Flex applications because Flex keeps the connection open / session alive on the server. - Flex keeps the connection alive by periodically pinging the server. - Sessions will never timeout due to this behavior. - When the user navigates away from the Flex application the session will timeout on the server. - To manually timeout a session on the server call a page or function that executes this code session.destroy( ); -- not sure what the recommended method to clear the session on the server. Any answers will help even partial. -- 8:00? 8:25? 8:40? Find a flickhttp://tools.search.yahoo.com/shortcuts/?fr=oni_on_mail#newsin no time with theYahoo! Search movie showtime shortcut.http://tools.search.yahoo.com/shortcuts/?fr=oni_on_mail#news
Re: [flexcoders]PHP and Flex questions
When a Flex application in a browser
communicates with a php page for the first time a session is created.
This is the same behavior as user receiving a PHP page in their
browser.
- true , but the session is created only if the php installed in your server
is configured to auto start a session or you manually start the session in your
scrip.
- This session that is created last indefinitely with Flex
applications because Flex keeps the connection open / session alive on
the server.
I am not sure if this is 100% true , but i believe by default , the http
headers send Connection: Keep-Alive, so sessions remain alive. In my
application it works okay, session doesn't expire while flex application runs.
However, I believe if you send custom HTTP headers this behavior can be lost.
- Flex keeps the connection alive by periodically pinging the server.
same as above
- Sessions will never timeout due to this behavior.
same as above
- When the user navigates away from the Flex application the session will
timeout on the server.
true , it will timeout in the time specified in your php.ini
To manually timeout a session on the server call a page or function that
executes this code
session.destroy( ); -- not sure what the recommended method to clear the
session on the server.
- true , depending on your php session you will call the correct function to
destroy the session
Hope this helps.
- Original Message
From: dorkie dork from dorktown [EMAIL PROTECTED]
To: flexcoders@yahoogroups.com
Sent: Tuesday, April 3, 2007 8:37:15 PM
Subject: [flexcoders]PHP and Flex questions
Can
someone tell me if these statements are true or false and if false what is
the correct answer?
- When a Flex application in a browser
communicates with a php page for the first time a session is created.
This is the same behavior as user receiving a PHP page in their
browser.
- This session that is created last indefinitely with Flex
applications because Flex keeps the connection open / session alive on
the server.
- Flex keeps the connection alive by periodically pinging the server.
- Sessions will never timeout due to this behavior.
- When the user navigates away from the Flex application the session will
timeout on the server.
- To manually timeout a session on the server call a page or function that
executes this code
session.destroy( ); -- not sure what the recommended method to clear the
session on the server.
Any answers will help even partial.
!--
#ygrp-mlmsg {font-size:13px;font-family:arial, helvetica, clean, sans-serif;}
#ygrp-mlmsg table {font-size:inherit;font:100%;}
#ygrp-mlmsg select, input, textarea {font:99% arial, helvetica, clean,
sans-serif;}
#ygrp-mlmsg pre, code {font:115% monospace;}
#ygrp-mlmsg * {line-height:1.22em;}
#ygrp-text{
font-family:Georgia;
}
#ygrp-text p{
margin:0 0 1em 0;}
#ygrp-tpmsgs{
font-family:Arial;
clear:both;}
#ygrp-vitnav{
padding-top:10px;font-family:Verdana;font-size:77%;margin:0;}
#ygrp-vitnav a{
padding:0 1px;}
#ygrp-actbar{
clear:both;margin:25px 0;white-space:nowrap;color:#666;text-align:right;}
#ygrp-actbar .left{
float:left;white-space:nowrap;}
.bld{font-weight:bold;}
#ygrp-grft{
font-family:Verdana;font-size:77%;padding:15px 0;}
#ygrp-ft{
font-family:verdana;font-size:77%;border-top:1px solid #666;
padding:5px 0;
}
#ygrp-mlmsg #logo{
padding-bottom:10px;}
#ygrp-vital{
background-color:#e0ecee;margin-bottom:20px;padding:2px 0 8px 8px;}
#ygrp-vital #vithd{
font-size:77%;font-family:Verdana;font-weight:bold;color:#333;text-transform:uppercase;}
#ygrp-vital ul{
padding:0;margin:2px 0;}
#ygrp-vital ul li{
list-style-type:none;clear:both;border:1px solid #e0ecee;
}
#ygrp-vital ul li .ct{
font-weight:bold;color:#ff7900;float:right;width:2em;text-align:right;padding-right:.5em;}
#ygrp-vital ul li .cat{
font-weight:bold;}
#ygrp-vital a {
text-decoration:none;}
#ygrp-vital a:hover{
text-decoration:underline;}
#ygrp-sponsor #hd{
color:#999;font-size:77%;}
#ygrp-sponsor #ov{
padding:6px 13px;background-color:#e0ecee;margin-bottom:20px;}
#ygrp-sponsor #ov ul{
padding:0 0 0 8px;margin:0;}
#ygrp-sponsor #ov li{
list-style-type:square;padding:6px 0;font-size:77%;}
#ygrp-sponsor #ov li a{
text-decoration:none;font-size:130%;}
#ygrp-sponsor #nc {
background-color:#eee;margin-bottom:20px;padding:0 8px;}
#ygrp-sponsor .ad{
padding:8px 0;}
#ygrp-sponsor .ad #hd1{
font-family:Arial;font-weight:bold;color:#628c2a;font-size:100%;line-height:122%;}
#ygrp-sponsor .ad a{
text-decoration:none;}
#ygrp-sponsor .ad a:hover{
text-decoration:underline;}
#ygrp-sponsor .ad p{
margin:0;}
o {font-size:0;}
.MsoNormal {
margin:0 0 0 0;}
#ygrp-text tt{
font-size:120%;}
blockquote{margin:0 0 0 4px;}
.replbq {margin:4;}
--
We won't tell. Get more on shows you hate to love
(and love to hate): Yahoo! TV's Guilty Pleasures
Re: [flexcoders]PHP and Flex questions
Rather than worry about the server session why not simply maintain the session state in the client since it is assume your client is running a SWF ala Flex. The fact that the client has accomplished a login could be handled by sending a specific token to the server as long as the token is some kind of UUID value that is known to be random yet non-sequential. I have coded this into a Flex Object that subclasses the HTTPService and once setup needs no further maintenance. In my specific case my app is always logged-in since it runs via an Intranet however my initial HTTPService call gets the user's metadata from the server and then I pass the user's ID back to the server on each HTTPService call but this is done transparently. Just a suggestion. I realize this may not be in keeping with the way most people might apprach this sort of problem. - Original Message From: dordea cosmin [EMAIL PROTECTED] To: flexcoders@yahoogroups.com Sent: Wednesday, April 4, 2007 1:27:44 AM Subject: Re: [flexcoders]PHP and Flex questions When a Flex application in a browser communicates with a php page for the first time a session is created. This is the same behavior as user receiving a PHP page in their browser. - true , but the session is created only if the php installed in your server is configured to auto start a session or you manually start the session in your scrip. - This session that is created last indefinitely with Flex applications because Flex keeps the connection open / session alive on the server. I am not sure if this is 100% true , but i believe by default , the http headers send Connection: Keep-Alive, so sessions remain alive. In my application it works okay, session doesn't expire while flex application runs. However, I believe if you send custom HTTP headers this behavior can be lost. - Flex keeps the connection alive by periodically pinging the server. same as above - Sessions will never timeout due to this behavior. same as above - When the user navigates away from the Flex application the session will timeout on the server. true , it will timeout in the time specified in your php.ini To manually timeout a session on the server call a page or function that executes this code session.destroy( ); -- not sure what the recommended method to clear the session on the server. - true , depending on your php session you will call the correct function to destroy the session Hope this helps. - Original Message From: dorkie dork from dorktown dorkiedorkfromdorkt [EMAIL PROTECTED] com To: [EMAIL PROTECTED] ups.com Sent: Tuesday, April 3, 2007 8:37:15 PM Subject: [flexcoders] PHP and Flex questions Can someone tell me if these statements are true or false and if false what is the correct answer? - When a Flex application in a browser communicates with a php page for the first time a session is created. This is the same behavior as user receiving a PHP page in their browser. - This session that is created last indefinitely with Flex applications because Flex keeps the connection open / session alive on the server. - Flex keeps the connection alive by periodically pinging the server. - Sessions will never timeout due to this behavior. - When the user navigates away from the Flex application the session will timeout on the server. - To manually timeout a session on the server call a page or function that executes this code session.destroy( ); -- not sure what the recommended method to clear the session on the server. Any answers will help even partial. 8:00? 8:25? 8:40? Find a flick in no time with theYahoo! Search movie showtime shortcut.
Re: [flexcoders]PHP and Flex questions
thank you On 04 Apr 2007 01:27:44 -0700, dordea cosmin [EMAIL PROTECTED] wrote: When a Flex application in a browser communicates with a php page for the first time a session is created. This is the same behavior as user receiving a PHP page in their browser. - true , but the session is created only if the php installed in your server is configured to auto start a session or you manually start the session in your scrip. - This session that is created last indefinitely with Flex applications because Flex keeps the connection open / session alive on the server. I am not sure if this is 100% true , but i believe by default , the http headers send Connection: Keep-Alive, so sessions remain alive. In my application it works okay, session doesn't expire while flex application runs. However, I believe if you send custom HTTP headers this behavior can be lost. - Flex keeps the connection alive by periodically pinging the server. same as above - Sessions will never timeout due to this behavior. same as above - When the user navigates away from the Flex application the session will timeout on the server. true , it will timeout in the time specified in your php.ini To manually timeout a session on the server call a page or function that executes this code session.destroy( ); -- not sure what the recommended method to clear the session on the server. - true , depending on your php session you will call the correct function to destroy the session Hope this helps. - Original Message From: dorkie dork from dorktown [EMAIL PROTECTED] To: flexcoders@yahoogroups.com Sent: Tuesday, April 3, 2007 8:37:15 PM Subject: [flexcoders]PHP and Flex questions Can someone tell me if these statements are true or false and if false what is the correct answer? - When a Flex application in a browser communicates with a php page for the first time a session is created. This is the same behavior as user receiving a PHP page in their browser. - This session that is created last indefinitely with Flex applications because Flex keeps the connection open / session alive on the server. - Flex keeps the connection alive by periodically pinging the server. - Sessions will never timeout due to this behavior. - When the user navigates away from the Flex application the session will timeout on the server. - To manually timeout a session on the server call a page or function that executes this code session.destroy( ); -- not sure what the recommended method to clear the session on the server. Any answers will help even partial. -- 8:00? 8:25? 8:40? Find a flick in no time with theYahoo! Search movie showtime shortcut.
