[EMAIL PROTECTED] Thu Apr 08 11:32:32 2004 Return-Path: <[EMAIL PROTECTED]> X-Sender: [EMAIL PROTECTED] X-Apparently-To: [email protected] Received: (qmail 93452 invoked from network); 8 Apr 2004 12:29:41 -0000 Received: from unknown (66.218.66.172) by m11.grp.scd.yahoo.com with QMQP; 8 Apr 2004 12:29:41 -0000 Received: from unknown (HELO n34.grp.scd.yahoo.com) (66.218.66.102) by mta4.grp.scd.yahoo.com with SMTP; 8 Apr 2004 12:29:41 -0000 Received: from [66.218.67.156] by n34.grp.scd.yahoo.com with NNFMP; 08 Apr 2004 12:28:44 -0000 Date: Thu, 08 Apr 2004 12:28:41 -0000 To: [email protected] Message-ID: <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> User-Agent: eGroups-EW/0.82 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Length: 1684 X-Mailer: Yahoo Groups Message Poster X-eGroups-Remote-IP: 66.218.66.102 From: "dharfleet" <[EMAIL PROTECTED]> X-Originating-IP: 80.225.165.43 Subject: Re: Flex Needs Remote Shared Objects! X-Yahoo-Group-Post: member; u=65830148 X-Yahoo-Profile: dharfleet
Hey All, personally I think this thread should be re-named 'messaging in Flex'. Stacey, "HHmm. That would cross the barrier from flex being a pure presentation server to a presentation server with a "hint" of app server functionality. ;-)" .... not sure I agree, the app server functionality would be the message server / MOM , the presentation server would just be acting as a client to the MOM, infact, I would imagine that it wouldn't even be a direct client, but would essentially be talking to a 'proxy' in the 'flex web-app' on the server, which would be the client to the MOM. Maybe flex can generic "messaging" API via web service or something. That way implementations would be same across Java/CF/.NET .... agree, I think you could have a MXML tag, similar to the remote object tag which would allow you to subscribe to a messaging topic / queue, this could be generic, or it could specify the 'proxy client' implementation which could be either JMS / MQSeries / Microsoft .net Messaging (?) / etc Libby, " > > Use cases, friends, use cases! It's definitely a feature we'll be > investigating but I'd love to hear as many specific use cases as possible." ..... any systems which rely on near realtime data to be updated on the users GUI without them requesting that update by 'clicking refresh'. For example: stock trading desk GUIs monitoring applications, such as weather, traffic, building security, manufacturing, gps parcel tracking mission critical systems, such as air traffic, utility supply, etc ...... great product and great yahoo group by the way; as a Java/J2EE developer, I would now feel comtable implementing a Macromedia GUI, Dan
