Whenever I consider something like this I try to put it in persective and testing each solution based on:
- ease of implementation (coding time) - speed of execution - flexibility for reuse in other projects And then make my decision based on this. I know it's probably not the answer you were looking for. Cheers, Adam ----- Original Message ----- From: Kevin To: [email protected] Sent: Saturday, March 17, 2007 11:07 AM Subject: [flexcoders] What to do on the server, what to do in Flex? I have a continuous debate with myself about what to accomplish with server code and what to accomplish internally with FLEX. My decisions currently are mostly based on my skill level in each language and which language makes the process the easiest. However, I am wondering if there are better reasons to make these decisions. For example, if I am going to gather some XML data...should I? 1) Load the XML directly into Flex (URLRequest) and then convert the XML to objects in Flex. 2) Load the XML in PHP and then convert to PHP objects and send to Flex (AMFPHP). For some reason, I lean towards doing all parsing and object translation on the server and only sending objects back and forth to Flex, however, I don't know if this is because of my experience with Flash RIA's that use to often get stuck in timeout loops. On the other hand, I have a friend who always says "anything you can do on the client, do on the client..." Conceptually, I understand this, but in real life I don't know how this plays out. My thinking is usually that the flash player is more limited that the server. Anyone have any thought about this? I would say my apps generally fall in the middle of the spectrum. They don't deal with millions of records or millions of users, but they also are not small single user widgets. Thanks for your insight. - Kevin
