On Sat, Mar 7, 2009 at 8:38 AM, David Adams <[email protected]> wrote:
> On Sat, Mar 7, 2009 at 2:06 AM, valdhor <[email protected]> wrote:
>> You still avoid telling us your back-end setup.
>>
>> I give up.
I figure I should address the next obvious suggestion in advance. Is
something like the following possible?
[Flash Player] <--- AMF---> [Apache + Zend] <--- XML or
something---> [4D]
Yes, it's entirely possible to put Apache (or what have you) into what
amounts to a smart proxying roll. It's even possible this setup would
deliver performance gains and other useful features as a bonus. There
are definitely times this would be well worth considering, but right
now I'm focusing on what can be done without the extra layer of
software. I'm well-enough versed in the specifics of this back-end
that what I've been trying to sort out is what is native and
reasonable in the Flash player. It's on the client side that I'm
ignorant. As in so many other areas of my life;-) But, pertinent to
this list, I'm ignorant about many aspects of the Flash player and the
Flex framework - the framework is huge and many features are easy to
overlook.
So far it looks like (ignoring back-end):
* AMF - Native
* XML - Native
* JSON - Often used library
* Plain-text format - May be able to leverage native features such as
String.split() or a custom parser that reads lengths precisely.
* Any of the textual formats (XML, JSON, plain-text of whatever sort)
may benefit from compression, depending on payload size,
compression/decompression time, and network conditions (latency and
bandwidth).
That's what I've got so far.
