Updated The GAE SWF Project (v1.20)
I just updated The GAE SWF Project to version 1.20 on appspot.
The Updated The GAE SWF Project (v1.20) article by Aral Balkan, unless otherwise expressly stated, is licensed under a Creative Commons Attribution-Noncommercial 2.0 UK: England License.
A quick list of changes:
- Pulled out
BaseViewandBaseApplicationclasses. - Simplified service calls. You no longer have to use Service.call() and pass a reference to the view instance. Just use
execute("service.method", arg1, arg2, ...). - Fixed a bug where the app was remembering the initial deep link on logout. Logouts now take you to the root of your Flash app.
The big change is that I've pulled out base application functionality so that your Application class now only contains logic specific to your particular application and not to GAE SWF applications in general.
Check out The GAE SWF Project on appspot.
The Updated The GAE SWF Project (v1.20) article by Aral Balkan, unless otherwise expressly stated, is licensed under a Creative Commons Attribution-Noncommercial 2.0 UK: England License.
]a[
Abstraction, abstraction, necessary but, nicely done. I’m with you for this ride
April 20th, 2008 at 1:50 amHerm Greider
Wow, incredible work! I’m not AMF-literate, so likely my lack of knowledge, but is there a way to unserialize the GAE Model objects on the Flash side? You display:
_User__email = myemail {at} xyz(.)com
Can that be used with something like “user.email”?
April 20th, 2008 at 3:26 pmImrahil
Great work! I’m waiting for more Flex examples!
April 20th, 2008 at 7:50 pmAral
Hi Herm,
It’s just because I’m passing the raw user object from Python back and that’s how the properties are in it (you’re getting the response from the users.get_current_user() method in webapp.)
You can easily create a simpler object and return that (I’m doing that in several of the calls.) That a look at the login() method in /services/user.py (and also checkout the ProfileVO object in the updateProfile() method of the same module.
April 20th, 2008 at 8:45 pmAral
Hi Imrahil,
It’s coming
April 20th, 2008 at 8:46 pmJavier
Yeah, I had to replicate my domain classes with simple VOs in order to make it work with pyamf. If you try to send an object (db.Model) with References on it pyamf crashes. It has issues serializing these objects
So in my model package I have normally a VO per model class to do the transfer…
I would like to be able to do like with JPA in Java that I can just send objects to the client, modify them there, send them back and automatically reattached them to the persistence layer. In this case you have to make the work on the services, or DAOS if you have them, of reconstructing objects in order to persist them.
I am very interested on what other people are doing architecting their applications on the Python side.
By the way I have the AMFPHP Browser working with PyAMF and your GAESWF project. It is quite handy for testing the services.
Thanks Aral!
April 21st, 2008 at 12:12 amHerm Greider
Aral, that makes sense. Perhaps I expect too much, but I want the more complex Model objects to deserialize correctly without additional work. Like Java
Javier, you have the same idea. I want automatic deserialization on the raw object.
So, I’m not convinced on pyAMF yet. I’m currently working with JSON off a plain HttpService. That seems to be close. With the example Pet Model, I can do this Flex-side:
// result is a set of JSON serialized pets
var rawData:String = String(event.result);
var pets:Array = (JSON.decode(rawData) as Array);
for (var i:int=0; i<pets.length; i++) {
var pet:Object = pets[i];
// you gotta use object.fields, but at least it’s a real object
status_txt.text += “Name: ” + pet.fields.name + “\n”;
status_txt.text += “Type: ” + pet.fields.type + “\n”;
}
I’ll document that more fully if I get it all working.
Thanks for the discussion anyway. All cool work.
April 21st, 2008 at 12:59 amJavier
Hey Herm,
I still think pyamf is a better solution that json for this work. Specially considering that in json there is almost no support for circular references, and this is quite handy!
So that pyamf does not support right now google’s objects for serialization I think is a matter of time. I am sure these guys will be working on that. Then probably there will be no need for most VO and only for some specific classes where you really need a transfer object instead of the raw model objects.
In any case I have the impression we will have to change our mind a little bit from the java world and their relational persistence frameworks, as this is not the same as Big Table in Google.
April 21st, 2008 at 6:58 pmNick Joyce
@Javier, @Herm: PyAMF does support serialising Google’s Model and Expando classes out of the box in version 0.3 and up. We’ll put up a complex model example as soon as time permits ..
We are in the middle or prepping 0.3.1 which will add more compatibility for frameworks like Google App Engine etc.
April 22nd, 2008 at 11:26 amThijs Triemstra
@Herm: see http://pyamf.org/ticket/307 for workarounds and progress for that issue with the PyAMF GAE adapter.
July 3rd, 2008 at 10:23 pm