--- In [email protected], "James" <garymoorcroft_...@...> wrote: > > Hi Amy. Sorry I missed your post yesterday. e4x does seem good but I was just > a little bit worried about implementing it. As a flex beginner I tend to > stick to the traditional most widely used methods of doing things as a lot of > the times I work by looking at previous examples and applying them to my own > code and it's hard to find examples of things such as handling results of e4x > etc.
Hi, James; If you want to do things in the traditional most widely used method, then you _definitely_ want to go with using e4x. To be blunt, what Robert has told you to do is a newbie workaround, which could easily have been avoided by just using e4x. It's unfortunate that "object" is the default return type for HTTPService, but it's very easy and quick to figure out how to fix it, especially if you read the FAQ's for this group. When you have a ton of extra code to implement an unnecessary workaround, it's just that much more code to maintain, bloats your file size, and slows performance. And, as Tracy says, in this particular instance, you also risk your data integrity. If you're worried about working with e4x, I found this guide very helpful when I first was learning it http://dispatchevent.org/roger/as3-e4x-rundown/. However, I'd agree with Steve that if you need to pass data both ways, you're probably better off using RPC remoting. If you're interested in AMFPHP, you can get a fully working example here: http://flexdiary.blogspot.com/2009/01/lazy-loading-tree-example-file-posted.html HTH; Amy
