The GAE SWF Project 1.21 1.23
I just updated The GAE SWF Project to version 1.21 1.23. New source code for the update is now available for download.
The The GAE SWF Project 1.21 1.23 article by Aral Balkan, unless otherwise expressly stated, is licensed under a Creative Commons Attribution-Noncommercial 2.0 UK: England License.
All changes in this version are server-side:
- All requests apart from those to the PyAMF gateway go through the
IndexHandlerclass. The app.yaml file no longer maps /examples/.* URLs to the various example SWF applications. In other words, the SWF apps are simply handler classes now, not separate WSGI applications. The PyAMF gateway remains a separate WSGI application. - Pulled out the server-side deep linking code from the initial example to a new
BaseSWFHandlerclass in the new gaeswf package. The handlers for all SWF examples will extend this class and call thehandleDeepLink()method to have regular deep links automatically converted to SWFAddress deep links. - Removed the unnecessary examples and initial packages and placed all examples in the root of the examples package.
- Added 404 handling. Unknown URLs no longer fail silently.
- main.html template is now known as base.html.
- Added simple.html template for handlers that want to use base.html without the need for a separate template that extends it.
Update: I've updated the online version to 1.23 to change the 404 photo. I realized this morning that the original Creative Commons-licensed photo I had found on Flickr did not belong to the user who had published it on their account.)
The The GAE SWF Project 
Rostislav
Hey Aral,
you’re pretty quick with one and it looks like a good reason to try the GAE offering.
The deep linking redirection should be done differently if you’re looking into search engine indexing. I’ll be glad to help you on this.
Cheers,
April 20th, 2008 at 10:31 pmRostislav
Aral
Hey Rostislav,
Thanks for the kind words. I just released the Flex version of the sample.
About the deep linking: my focus is not SEO but usability but I’d love to hear your thoughts. Were you suggesting something along the lines of the approach in the SEO samples in SWFAddress?
(Oh, and great work on SWFAddress, by the way. Very, very, important!)
April 22nd, 2008 at 8:43 amRostislav
If it’s just usability then the redirection from /regular-link to /#/deep-link doesn’t help much. It’s 2 symbols less but overall brings the same functionality. On the other hand it can be indexed compared to the anchor version.
For some reason only after the redirect I get a SWFAddress JS error in IE7. I should download the GAE SDK and try it locally when I find some time available.
April 22nd, 2008 at 9:16 pmAral
Hi Rostislav,
I’d love to hear your thoughts once you’ve had a chance to look at the code. Looking forward to your involvement.
April 23rd, 2008 at 1:39 pm