as3httpclient project update

Sometimes back, I posted about as3httpclient project which is an open-source http-protocol-library written in ActionScript 3, not yet completely done. Library has been updated recently by Erik, who has recently joined the project. It’s great to have him in the team.

Things that have changed:-

  • package name has been changed to* from*;
  • HTTPURLLoader class has been renamed to SocketURLLoader
  • Some more classes added.
  • ASDocs has been added.

Now as3httpclient can be used for:-

  • HTTP Basic Authentication without browser’s dialogue box
  • Adding custom or standard HTTP headers
  • Uploading files to server that requires http-authentication [new]
  • Copying bytes (of images/files downloaded using this library).

Two important features planned for future release:-

  • Support for more HTTP verbs (PUT, DELETE, OPTIONS, HEAD etc) – would be there soon.
  • Support for SSL or Secure HTTP – This feature might take sometime because it needs some investigation.

Please check out the project. I would love to hear your feedback/bug-reports/suggestions.

Please get back in touch with me [mail at abdulqabiz dot com], if you want to contribute to the project.

Technorati tags: , ,

  • Johanna

    Hi Abdul,
    thanks a lot for your work on this whole authentication issue!
    I’m pretty new to AS3 and I guess that’s why I’m struggling with the bloglines-example from your earlier post. I just can’t get it to work.
    Apparently the EventListeners defined for “complete”, “httpStatus” and “progress” are not invoked, so nothing happens.
    Do you have any ideas what I’m doing wrong?
    Thanks a lot and many greets from Germany to India,

  • @Johanna: I also noticed this, I would look at it and let you know the solution.
    Thanks for the greetings, I wish you the same from India 🙂

  • Kieran Metcalfe

    Hi Abdul
    I’ve been trying to get this to work too – It looks like the events aren’t firing because if you run it on a remote host, the crossdomain.xml / policy stuff doesn’t allow socket connections on ports below 1024.
    I’ve not come up with a way around it – have you?