AMFPHP - is it statless?

Great_Late · 07-09-2003, 09:42 AM

I've been digging and have installed and written a few simple AMFPHP examples.

The question I have is three part.

1. Is the flash remoting connection stateless? The tutorial on this site says the connection from the clients end at least is on until it's terminated. It would then stand to reason that the server-side also holds information about the connection. Which leads me to my next question.

2. Is there a way to keep persistent data like a login record on the server. My concern is security. The less I pass sensitive information the happier I'll be. As well as the least work my server has to do retrieving it repeatedly is fine by me.

3. I've read alot of what macromedia has to say about security. And from what I've gathered since the gateway in reached through http, It can also be reached through https. Are there any other known holes in the pipe?

Thanks in advance for your help.

freddycodes · 07-09-2003, 10:45 PM

Its not exactly stateless as I see it, I mean every call to the server regardless of the connection is a http request. So in order to have a pseudo stateless data stored in the database you would need to pass some sort of unique identifier back and forth on every call.

In order to have a persistent stateless connection you would need to use Sockets.

Great_Late · 07-10-2003, 01:27 AM

Yeah. Thats what I thought. I started with sockets and was having some trouble securing the connection. Like I couldn't find anyone that even talked about it. You got any suggestions.

Thanks.

freddycodes · 07-10-2003, 01:32 AM

What do you want to know? I have worked fairly extensively with socket communications involving flash and PHP and PERL.

Your main obstacle with securing the connection is that Flash has no native way to encrypt data over sockets. You can send data over https but that is not a persistent connection. There are some one way encryption algorithms but as far as two way encryption its just not possible with flash yet.

Great_Late · 07-10-2003, 02:36 AM

That's what I've recently figured out after figuring out how to connect to a socket and maintain connection.

Everything with AMFPHP is over http correct?

I guess I'll have to use session to maintain info.

Are you aware of any restrictions with service sizes? I tried to convert my app to work with remoting and built a service to contain it all and for some reason when ever I include/require my library files it stops working. If I build the functions in the service it works, but if I try to use lib files it chokes.

Thanks a lot for all your help.

07-09-2003, 09:42 AM	#1
Great_Late Registered User Join Date: Jul 2003 Posts: 5	AMFPHP - is it statless? I've been digging and have installed and written a few simple AMFPHP examples. The question I have is three part. 1. Is the flash remoting connection stateless? The tutorial on this site says the connection from the clients end at least is on until it's terminated. It would then stand to reason that the server-side also holds information about the connection. Which leads me to my next question. 2. Is there a way to keep persistent data like a login record on the server. My concern is security. The less I pass sensitive information the happier I'll be. As well as the least work my server has to do retrieving it repeatedly is fine by me. 3. I've read alot of what macromedia has to say about security. And from what I've gathered since the gateway in reached through http, It can also be reached through https. Are there any other known holes in the pipe? Thanks in advance for your help.

Thread Tools
Show Printable Version Email this Page
Display Modes	Rate This Thread
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode	Rate This Thread:

07-09-2003, 10:45 PM	#2
freddycodes Master of Nothing Join Date: Dec 2002 Location: San Diego, CA Posts: 2,468	Its not exactly stateless as I see it, I mean every call to the server regardless of the connection is a http request. So in order to have a pseudo stateless data stored in the database you would need to pass some sort of unique identifier back and forth on every call. In order to have a persistent stateless connection you would need to use Sockets.


<a href='http://d1.openx.org/ck.php?n=ac86e9f0&cb=INSERT_RANDOM_NUMBER_HERE' target='_blank'><img src='http://d1.openx.org/avw.php?zoneid=36053&source=_blank&cb=INSERT_RANDOM_NUMBER_HERE&n=ac86e9f0' border='0' alt='' /></a>

07-10-2003, 01:27 AM	#3
Great_Late Registered User Join Date: Jul 2003 Posts: 5	Yeah. Thats what I thought. I started with sockets and was having some trouble securing the connection. Like I couldn't find anyone that even talked about it. You got any suggestions. Thanks.

07-10-2003, 01:32 AM	#4
freddycodes Master of Nothing Join Date: Dec 2002 Location: San Diego, CA Posts: 2,468	What do you want to know? I have worked fairly extensively with socket communications involving flash and PHP and PERL. Your main obstacle with securing the connection is that Flash has no native way to encrypt data over sockets. You can send data over https but that is not a persistent connection. There are some one way encryption algorithms but as far as two way encryption its just not possible with flash yet.

07-10-2003, 02:36 AM	#5
Great_Late Registered User Join Date: Jul 2003 Posts: 5	That's what I've recently figured out after figuring out how to connect to a socket and maintain connection. Everything with AMFPHP is over http correct? I guess I'll have to use session to maintain info. Are you aware of any restrictions with service sizes? I tried to convert my app to work with remoting and built a service to contain it all and for some reason when ever I include/require my library files it stops working. If I build the functions in the service it works, but if I try to use lib files it chokes. Thanks a lot for all your help.