Hmm, e4x is working pretty well in beta 1
as far as I know. But binding from e4x was not really supported well though
that support is better in b2 (I responded to another thread about this today I think). I think lots of XML transferring back and
forth is generally not the most efficient because it’s usually not
compressed. Even if you don’t want to tie yourself to a specific RDBMS
there are server techniques (like Hibernate or DataAccessObjects) that abstract
the DB away from you. You can then use more efficient transfer mechanisms like
RemoteObject with AMF. But it’s really a matter of what’s right
for your use-case. Matt From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf
Of Jason Hawryluk Thanks for the response Matt :) I am trying to exclusively use e4x for
exchanging data between the server and the client. I have a growing assumption
that the e4x implementation is not quite ready in beta 1 based on the fact that
often I need to devise a work around in order to properly use it. Am I correct?
For example binding sometimes causes
binding warnings. I'm seeing that results returned/converted on the client
to objects (not a formatted result as e4x) seem to behave better, and
are smoother for Flex to consume. 80% of the data the client is consuming is
stored as xml on the server. Not sure if it's the best way to do things but I
want to eliminate as much as possible being locked into a specific RDMS. That
said the DB is basically just for file lookup, search indexing, and user
profiles. Direct Disk access is much faster and
consumes less resources then having your web service poll the db, then
transform to xml then send over the wire. Especially when working with multiple
table relationships. Say if a Task can be related to many contacts. Storing
this relation in xml gets rid of allot of overhead on the server side, and
seems natural for xml file formats. I need to be able to load it, modify it,
then send it back in a xml format to a web service which has the job of
serializing the physical file to the users storage space. This has gotten off topic, sorry. I should
probably start a new post, but what is (if there is) the preferred way to
store/access data from your point of view? Anyone else please jump in here ;) Jason -----Message d'origine-----
|
- RE: [flexcoders] XMLEncoder Question [Flex 2.0 b1] Matt Chotin
- RE: [flexcoders] XMLEncoder Question [Flex 2.0 b1] Jason Hawryluk