> I guess long story short, stick with JSON, REST, SOAP, etc... it will make
> future expansion easier (if you can see it going that route).
That's a little too short for me. Not everything is likely to expand
beyond wildest expectations, so sometimes PyAMF will be the way to go.
Unfortunately,
Yup, I was going to reply with this as well. One draw back to this, however,
is that it makes the app a little bit more complicated to test and debug,
I've found, unless you concoct your own other test cases that import the
pyAmf libs and test separately. Another thing you might want to think about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
solar declared:
> Is there a 'common' way to build apps with django and a Adobe Flex
> frontend?
> I'm about to do just that, and I'm a bit overwhelmed by the number of
> choices that you get by multiplying
> communication layers (REST, XML-RPC, S
3 matches
Mail list logo
