On Apr 16, 2010, at 7:27 AM, Pascal wrote: > If I stored the Stack in the Session directly, I would need to copy most > of the FlashScope functionality, especially adding a parameter that > identifies each window (when the user has several tabs open with the > application) and removing stale Stacks after some timeout, which I'd > like to avoid.
FlashScope is one of those things that was dipped straight out of the river Styx. It's only use is to take you and your app straight to Hell. My favorite aspect of FlashScope is using it to render a page and then, being twisted that way, hitting the Refresh button and watching my page fall completely apart because whatever was in FlashScope before to make it pretty and informative, most certainly isn't now. FlashScope is just awful. I appreciate it's occasional usefulness. You know, like just having coffee with Faust rather than signing any of his papers. But most certainly don't use it for anything important. Combining FlashScope with running a webapp from several, simultaneous tabs within a single browser, and somehow expecting each page to maintain their own private little personal conversation with the backend automagically, and having them not get mixed up -- well, that's, frankly, just utter madness. You may as well shave your head now and get it over with. Though I would suggest some nice gloves to prevent scarring when you start to dig furrows in to you skull trying to get this to work. The lifespan of FlashScope is just that -- instant, in a flash. Like the glimpse of that girl just as she heads around the corner...but alas, she is gone and her memory is already fleeting. If only you knew her name... You simply can't rely on it for any length of time. Be grateful you got the glimpse after the redirect. As for supporting a webapp in multiple tabs or windows...oh dear... That's where you hunt down the girl and find she has a twin. Then you find that not only does she have a twin, it's an evil twin. Turns out they're both evil and they play tricks on you. Lying about who they are. Saying, "No, I'm Sally, SHE is Susan...can't you tell us apart"?? And, boy, you can just imagine where that trail leads... It's quite easy for a browser to make duplicate copies of pages to wit your app will not know the difference. You can try and make your own little session cookie...on every form...and every url...cuz, you know, it's a lot of fun. Then you have the browsers BACK button backing in to your application like a drunken UPS driver. Your server state just becomes a nightmare to manage -- with the potential of brown UPS paint smeared all over it, and you know what that would look like... I would put serious consideration in to this overall application path and the thinking, hopes and dreams behind it. FlashScope is the wrong tact, most certainly, and while what you want to do can ALMOST be done (almost...mostly...kinda), especially with a pure AJAX RIA app, if you choose to follow this path, that Faust guy might have some papers for you to sign. Regards, Will Hartung ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Stripes-users mailing list Stripes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-users
