December 16, 2007
Thinking About BlazeDS with Amazon ES2
With the current focus on Amazon's services (because of the release of SimpleDB) as well as the release of BlazeDS, I was wondering whether Amazon Elastic Compute Cloud (aka EC2) could be used with BlazeDS. I know that people set up Tomcat on EC2, and it'd be pretty interesting to start using BlazeDS on projects so easily.
Reading about EC2, I see that there's two ways to get data from your application, SOAP and a query API. The query API looks like it would work fine for getting AMF information from an application. I assume, however, that some changes some need to be made to Flex channels and adaptors to work with the request signatures required by Amazon? I don't know enough about EC2 or BlazeDS to answer this question, or to know whether StreamingAMFChannel would work. But I'd love see instructions on creating an Amazon Machine Image containing BlazeDS.
Sudden Flash Problems? Read About the Security Changes
If you're having complaints from customers about certain media not showing up or problems clicking on links, then I recommend reading about the security changes in Flash Player 9,0,115,0. Actually, I recommend reading the article no matter what, as there's a significant amount of changes.
I'm surprised there hasn't been more blog posts on this (although here's a recent one), as I generally keep up with mxna, and I haven't seen information on it. The changes caught me, and it'll be a good reminder to test new players while they are still in beta.
December 13, 2007
What's In Blaze DS?
So I'm not usually for the "me too" posts, but I'm excited enough to add to the blog overflow. The open sourcing of remoting and messaging is as big of news as the opening sourcing of the SDK. I won't rewrite what has already been said- see the posts by Christophe and Ted. But I couldn't find a detailed list of what's included in Blaze DS. I haven't paid much attention to Adobe Livecycle Photoshop Acrobat Data Service (that's the name, right?), and I don't know what comes with "remoting and messaging". Here's what I see from the examples in the download:
Sample 1: Accessing data using HTTPService
I assume this isn't just the HTTPService that gets the resource, but that it's using the HTTP proxy to get the resource. I know this piece pretty well, since I spent a long time working on it, way back in the day. It allows whitelists be set, simplifies some issues with data and the player, etc.
Sample 3: Accessing data using Remoting
AMF3 remoting, the piece that most people will be using, and which should need little explanation.
Sample 6: Publish/Subscribe Messaging (Data Push Use Case)
This is the "messaging" part of the release, and the part I definitely know the least about. It allows messages to be pushed to different clients with a minimal amount of work. The data is pushed with channels you can set up and use, both AMF and RTMP. And now there seems to be one more, "a new HTTP Streaming channel for real time applications that require very low latency." Exciting stuff!
Update: I assumed that RTMP was included for messaging, but according to a comment Dirk Eismann on Christophe's post, it isn't included. It looks like that's part of the reason the new HTTP channel was created.
If anybody has a more succinct list of what's included, I'd appreciate a link.