I don't think PUT it is implemented yet. The project has less attention now because of the new security restrictions on the latest Flash player.
These restrictions make the socket class less usefull. If you want to connect to a socket the Flash player needs authorisation, more about this can be found here: http://www.adobe.com/devnet/flashplayer/articles/fplayer9_security_04.html
The bottom line is:
- If you are using AIR to build your application, this is very doable and could be implemented using the Socket class
- If you are connecting to a server of your own, you would need a socket server on port 843 to grant access to the http socket. After that the feature could be implemented using the Socket class.
In your email you write:
It would be a bonus if it:
- Retried on failure and timeouts
- Had stop/resume capability
- UI was customizable
- Supported multiple files
- Had file upload progress bar
The FileReference class could help you with most of these things.
- Retried on failure and timeouts
You could add a listener for failure and let your code retry
- Had stop/resume capability
Not sure if this is available for FileReference
- UI was customizable
- Supported multiple files
- Had file upload progress bar
These can all be accomplished using FileReference.
Greetz Erik
I am very sorry to say, but using the AS3HTTPClient that will be
impossible. The AS3HTTPClient connects over a socket that has to obey
the security shizzle in the Flash player (the story about port 843).
>Would it support cookies?
It would not. Since the socket is not connecting over http using the
browser engine cookies are not accessible. The socket implements it's
own implementation of the http protocol and has no way to access
browser cookies. You could however implement cookie support yourself
as cookies are merely http headers.
>Authorization would only be using a cookie.
The autorization I meant was authorizing the Flash player to connect
using the socket class. This authorization can be done in 2 ways:
1. Serving a socket domain policy file on port 843
2. Serving a socket domain policy file on the port you are connecting
to (in case of http, port 80)
Greetz Erik