« Symbian's (and Nokia's) structural handicap | Main | Apps or web - what direction will RIM take? »

July 30, 2010

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8345a82d869e20133f2b72cab970b

Listed below are links to weblogs that reference Flash? Give it a REST:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

It seems you are not the only one to gripe about this. In fact others have encountered and made solutions available for this:

http://lab.arc90.com/2008/03/25/flex-as3-library-restservice/

You should read about REST anti-patterns. Cookies are one.

http://www.infoq.com/articles/rest-anti-patterns

Lionel: Indeed, anyone who tries to use Flash to access a real REST web service is in for the same pain. That's an interesting library you link to - alas it suffers from the pain of using sockets, which our experience tells us means it won't work for a lot of people sat behind corporate firewalls. Adobe have done a poor job of getting people to open port 843 so that sockets access works - and it's even hard to find a site you can use as a "checker" that the port is open/closed.

Hi Matt,

Here are some thoughts from my team mate Duane:
http://technoracle.blogspot.com/2010/07/soa-vs-rest-in-flash-player.html

Personally I'm all for it for the sake of productivity.

Mark

On the whole I agree with what you are saying, but is the criticism the fact that Flash/Flex is REST unfriendly, or more that it has subpar HTTP support? Given Flash's background (remember Macromedia Director?) and it's intended audience (typically not hardcore, latter-day services folk), maybe the HTTP support is reasonable, though not optimal.

If we're going to fault Flash for not respecting cookies because that's a browser thing, should we expect it to respect Cache-Control headers and maintain a cache? I find that a more powerful tool in the HTTP-based RESTful toolkit.

Jason, thats a good point.  The criticism is that Flash is sub-par for implementing access to REST services over HTTP, which in my view makes it REST-unfriendly.  Flash is definitely an evolved product rather than a designed one, and it clearly started a long way from where it ended up.  Given that, I agree the HTTP support could be seen as adequate even if it doesnt do REST well.  The catch is that Adobe are now promoting it as a native web citizen - and native web citizens really need to support the fundamental architecture of the web.

Malcolm

How do I make my flash game 2 players on one computer, and up to 4 online?

The comments to this entry are closed.

Blog powered by Typepad