RE: [Junk E-Mail - LOW] Re: [Junk E-Mail - MED] [flexcoders] A general Flex application deployment question..

[Shannon Hicks]

Paul said that the current application was great when it was working, but everyone hated it when it was slow or the internet connection was down. I was not implying that flex doesn't work, or that I couldn't connect to them. I was saying Flex has no built-in mechanism to handle when the connection with the server is severed.   I did a little quick research on sharedObjects... So if I need to store more than 10k of data, I need to get the user to change their flash settings? Seems like it's not terribly useful for maintaining a history of additions/changes of data for my app, should the connection between client & server drop. Hopefully I'm misunderstanding this, or Apollo will address these problems.   Shan     From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of hank williams Sent: Sunday, July 23, 2006 10:13 AM To: flexcoders@yahoogroups.com Subject: [Junk E-Mail - LOW] Re: [Junk E-Mail - MED] [flexcoders] A general Flex application deployment question.. On 7/23/06, Shannon Hicks <[EMAIL PROTECTED]> wrote: Flex, in it's present form, does not handle connectivity issues well. I'm not sure exactly what you mean by this. I have no problem "connecting" to flash/flex apps. Of course if the internet connection is down then things wont work, but that's not a flex issue.   While it's possible to do, Flex can't save anything to the user's local hard drive, so "saved" information is only saved while the browser window is open. Actually, flash has local sharedObjects that allow an application to save data locally.   Maybe some clever Flash guru can make me eat my words :)   However, if I understand correctly, Adobe's upcoming technology, Apollo, will allow for this sort of thing (a flex-built desktop app with limited / occasional connections to the server). I'm not sure he was concerned about occasional connections to the server. He simply said remotely served application. Shan From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Paul Andrews Sent: Sunday, July 23, 2006 6:13 AM To: flexcoders@yahoogroups.com Subject: [Junk E-Mail - MED] [flexcoders] A general Flex application deployment question.. My wife works in education and her school subscribes to a remote service that supplies web based information via the internet. When it works they love it but it's gotten a pretty awful nickname for the times it doesn't or is just plain slow. The important point here is that it's a good application, supplied from a remote server, but seen as unreliable either due to internet connectivity problems or speed. Forgetting the speed problem (there's usually ways to sort that out), I wondered how people are using Flex as a remotely served application. Are there good strategies to mitigate connection problems and how do companies react to the idea of remotely served applications that are important/critical to the business? Is the critical desktop application where Flex cannot go (except perhaps by in-house intranet)? Paul -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.10.3/395 - Release Date: 7/21/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.10.3/395 - Release Date: 7/21/2006 -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.10.3/395 - Release Date: 7/21/2006 __._,_.___ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com YAHOO! GROUPS LINKS  Visit your group "flexcoders" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. __,_._,___ -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.10.3/395 - Release Date: 7/21/2006