[EMAIL PROTECTED] Mon Apr 05 14:16:57 2004 Return-Path: <[EMAIL PROTECTED]> X-Sender: [EMAIL PROTECTED] X-Apparently-To: [email protected] Received: (qmail 21674 invoked from network); 5 Apr 2004 21:16:55 -0000 Received: from unknown (66.218.66.217) by m12.grp.scd.yahoo.com with QMQP; 5 Apr 2004 21:16:55 -0000 Received: from unknown (HELO ns2.sfcommerce.com) (204.92.58.42) by mta2.grp.scd.yahoo.com with SMTP; 5 Apr 2004 21:16:55 -0000 Received: from moc-gen-mai-31.corp.sfcommerce.com (moc-gen-mai-31.corp.sfcommerce.com [172.16.31.82]) Received: from moc-gen-mai-21.corp.sfcommerce.com (unverified) by moc-gen-mai-31.corp.sfcommerce.com (Content Technologies SMTPRS 4.3.6) with ESMTP id <[EMAIL PROTECTED]> for <[email protected]>; Mon, 5 Apr 2004 17:16:53 -0400 Received: from MOC-GEN-MAI-11.corp.sfcommerce.com ([172.16.31.81]) by moc-gen-mai-21.corp.sfcommerce.com with Microsoft SMTPSVC (5.0.2195.6713) ; Mon, 5 Apr 2004 17:16:53 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C41B53.511F8158" Date: Mon, 5 Apr 2004 17:16:53 -0400 Message-ID: <[EMAIL PROTECTED]> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [flexcoders] Flex Needs Remote Shared Objects! Thread-Index: AcQbUVs42C4Teos5QxGdZ4vJ8Tp5PAAAbpKA To: <[email protected]> X-OriginalArrivalTime: 05 Apr 2004 21:16:53.0155 (UTC) FILETIME=[512FF730:01C41B53] X-eGroups-Remote-IP: 204.92.58.42 From: "Dimitrios Gianninas" <[EMAIL PROTECTED]> Subject: RE: [flexcoders] Flex Needs Remote Shared Objects! X-Yahoo-Group-Post: member; u=181750851 X-Yahoo-Profile: angelone197555
------_=_NextPart_001_01C41B53.511F8158 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable And of course this will have to be tied to the middleware somehow, especially for point 3 of Stacy's email. So it would have to be a Java push? hmm.. don't know. =20 Maybe Flex handles doing the push, but gets data from some service and then sends it to all the client UIs. =20 Jimmy Gianninas - Software Developer Terra Payments Inc. (514) 380 - 2700 extension 3249 =20 _____=20=20 From: Libby Freligh [mailto:[EMAIL PROTECTED] Sent: Monday, April 05, 2004 5:03 PM To: [email protected] Subject: RE: [flexcoders] Flex Needs Remote Shared Objects! you guys are the bomb, as usual. thanks.=20 _____=20=20 From: Dimitrios Gianninas [mailto:[EMAIL PROTECTED] Sent: Monday, April 05, 2004 1:51 PM To: [email protected] Subject: RE: [flexcoders] Flex Needs Remote Shared Objects! Stace said it all... please put this in... I just got another idea from seeing M$ CRM. =20 As people work in Tech Support, they get notified of system trouble and such... using the ticketing system I've build with the Flex UI, they can send notifications to everyone logged in, specifically customer service to tell them of the problem. So that when they are on the phones, they will be able to quickly respond to customers. =20 Right now emailed is used. =20 Jimmy Gianninas - Software Developer Terra Payments Inc. (514) 380 - 2700 extension 3249 =20 _____=20=20 From: Stacy Young=20 Sent: Monday, April 05, 2004 4:44 PM To: [email protected] Subject: RE: [flexcoders] Flex Needs Remote Shared Objects! 1. Control Panel/Dashboard apps, pushing real-time monitoring data to the display. ( Biz metrics, CPU/Memory usage etc )=20 2. Multi-User applications. Any time data is relevant to many parties. Example would be ticketing application...customer service has application running 24/7 on their desktop...ticket statuses are pushed to clients as they're updated.=20 3. External "push" from outside systems (as Steven mentioned). Let's take the ticketing example once again, 'users' are not the only way for tickets to enter the system. We'd like all our products/services/systems to tie into this system. Real-time trouble-ticket creation. System A throws an exception which is caught and in turn 'fed' into system B in the form of a trouble ticket. (flex enabled ticketing system)=20 =20 Stace :D =20 _____=20=20 From: Libby Freligh [mailto:[EMAIL PROTECTED] Sent: Monday, April 05, 2004 2:43 PM To: [email protected] Subject: RE: [flexcoders] Flex Needs Remote Shared Objects! =20 =20 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. =20 l.=20 =20 _____=20=20 From: Steven Webster [mailto:[EMAIL PROTECTED] Sent: Sunday, April 04, 2004 1:57 AM To: [email protected] Subject: Re: [flexcoders] Flex Needs Remote Shared Objects! On Sun, 2004-04-04 at 04:49, Stacy Young wrote: > Here's a vote for a 1.x (one can hope) or a 2.x release of Flex. Add the > ability to push data to clients. Essentially a subset of features > offered by Flashcom...or more specifically, remote shared objects. That > would be SO killer...and would close the book on benefits of RIAs in the > biz world. I'll second this ... and more importantly, the ability to drive the "push" from the server-side application (which Flash Comm doesn't support directly). I guess this is quite a big ask though... Steven Yahoo! Groups Sponsor=09 ADVERTISEMENT click here <http://rd.yahoo.com/SIG=3D12ci7qksc/M=3D291630.4786521.5933964.1261774/D= =3Deg roupweb/S=3D1705007207:HM/EXP=3D1081285363/A=3D2072414/R=3D0/SIG=3D11tc61np= d/*http ://www.netflix.com/Default?mqso=3D60178418&partid=3D4786521>=20=09 =20 <http://us.adserver.yahoo.com/l?M=3D291630.4786521.5933964.1261774/D=3Degro= u pweb/S=3D:HM/A=3D2072414/rand=3D707839898>=20=09 _____=20=20 Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ =09=20=20 * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>=20 =09=20=20 * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service <http://docs.yahoo.com/info/terms/> .=20 <table width=3D800 cellpadding=3D4 cellspacing=3D10 border=3D0><tr bgcolor= =3DBDBDBD><td valign=3Dtop width=3D400><font face=3Dverdana size=3D2 color= =3DFFFFFF><b>AVIS IMPORTANT</b></font></td><td valign=3Dtop width=3D400><fo= nt face=3Dverdana size=3D2 color=3DFFFFFF><b>WARNING</b></font></td></tr><t= r><td valign=3Dtop width=3D400><p align=3Djustify><font face=3Dverdana size= =3D1 color=3D808080> Les informations contenues dans le present document et= ses pieces jointes sont strictement confidentielles et reservees a l'usage= de la (des) personne(s) a qui il est adresse. Si vous n'etes pas le destin= ataire, soyez avise que toute divulgation, distribution, copie, ou autre ut= ilisation de ces informations est strictement prohibee. Si vous avez recu c= e document par erreur, veuillez s'il vous plait communiquer immediatement a= vec l'expediteur et detruire ce document sans en faire de copie sous quelqu= e forme.</td><td valign=3Dtop width=3D400><p align=3Djustify><font face=3Dv= erdana size=3D1 color=3D808080> The information contained in this document = and attachments is confidential and intended only for the person(s) named a= bove. If you are not the intended recipient you are hereby notified that an= y disclosure, copying, distribution, or any other use of the information is= strictly prohibited. If you have received this document by mistake, please= notify the sender immediately and destroy this document and attachments wi= thout making any copy of any kind.</td></tr></table> ------_=_NextPart_001_01C41B53.511F8158 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR> <STYLE>@font-face { font-family: Wingdings; } @font-face { font-family: Tahoma; } @font-face { font-family: Bookman Old Style; } @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } A:link { COLOR: blue; TEXT-DECORATION: underline } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline } A:visited { COLOR: blue; TEXT-DECORATION: underline } SPAN.MsoHyperlinkFollowed { COLOR: blue; TEXT-DECORATION: underline } TT { FONT-FAMILY: "Courier New" } SPAN.EmailStyle18 { FONT-WEIGHT: normal; COLOR: blue; FONT-STYLE: normal; FONT-FAMILY: "Bookma= n Old Style"; TEXT-DECORATION: none } DIV.Section1 { page: Section1 } OL { MARGIN-BOTTOM: 0in } UL { MARGIN-BOTTOM: 0in } </STYLE> </HEAD> <BODY lang=3DEN-US vLink=3Dblue link=3Dblue> <DIV dir=3Dltr align=3Dleft><SPAN class=3D889151521-05042004><FONT face=3DA= rial=20 color=3D#0000ff size=3D2>And of course this will have to be tied to the mid= dleware=20 somehow, especially for point 3 of Stacy's email. So it would have to be a = Java=20 push? hmm.. don't know.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D889151521-05042004><FONT face=3DA= rial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D889151521-05042004><FONT face=3DA= rial=20 color=3D#0000ff size=3D2>Maybe Flex handles doing the push, but gets data f= rom some=20 service and then sends it to all the client UIs.</FONT></SPAN></DIV> <DIV> </DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2>Jimmy Gianninas - Software=20 Developer</FONT></DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2><STRONG>Terra Payments=20 Inc.</STRONG></FONT></DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2>(514) 380 - 2700 extension=20 3249</FONT></DIV> <DIV> </DIV><BR> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> <FONT face=3DTahoma size=3D2><B>From:</B> Libby Freligh=20 [mailto:[EMAIL PROTECTED] <BR><B>Sent:</B> Monday, April 05, 2004 5:= 03=20 PM<BR><B>To:</B> [email protected]<BR><B>Subject:</B> RE: [flexcod= ers]=20 Flex Needs Remote Shared Objects!<BR></FONT><BR></DIV> <DIV></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D541130521-05042004><FONT face=3DA= rial=20 color=3D#0000ff size=3D2>you guys are the bomb, as usual. thanks.=20 </FONT></SPAN></DIV><BR> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> <FONT face=3DTahoma size=3D2><B>From:</B> Dimitrios Gianninas=20 [mailto:[EMAIL PROTECTED] <BR><B>Sent:</B> Monday, Apr= il=20 05, 2004 1:51 PM<BR><B>To:</B> [email protected]<BR><B>Subject:</B= > RE:=20 [flexcoders] Flex Needs Remote Shared Objects!<BR></FONT><BR></DIV> <DIV></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D958094820-05042004><FONT face=3DA= rial=20 color=3D#0000ff size=3D2>Stace said it all... please put this in... I just = got=20 another idea from seeing M$ CRM.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D958094820-05042004><FONT face=3DA= rial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D958094820-05042004><FONT face=3DA= rial=20 color=3D#0000ff size=3D2>As people work in Tech Support, they get notified = of system=20 trouble and such... using the ticketing system I've build with the Flex UI,= they=20 can send notifications to everyone logged in, specifically customer service= to=20 tell them of the problem. So that when they are on the phones, they will be= able=20 to quickly respond to customers.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D958094820-05042004><FONT face=3DA= rial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D958094820-05042004><FONT face=3DA= rial=20 color=3D#0000ff size=3D2>Right now emailed is used.</FONT></SPAN></DIV> <DIV> </DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2>Jimmy Gianninas - Software=20 Developer</FONT></DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2><STRONG>Terra Payments=20 Inc.</STRONG></FONT></DIV> <DIV align=3Dleft><FONT face=3DArial size=3D2>(514) 380 - 2700 extension=20 3249</FONT></DIV> <DIV> </DIV><BR> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> <FONT face=3DTahoma size=3D2><B>From:</B> Stacy Young <BR><B>Sent:</B> Mond= ay, April=20 05, 2004 4:44 PM<BR><B>To:</B> [email protected]<BR><B>Subject:</B= > RE:=20 [flexcoders] Flex Needs Remote Shared Objects!<BR></FONT><BR></DIV> <DIV></DIV> <DIV class=3DSection1> <OL style=3D"MARGIN-TOP: 0in" type=3D1> <LI class=3DMsoNormal style=3D"COLOR: blue"><FONT face=3D"Bookman Old Sty= le"=20 color=3Dblue size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Bookman Old Style'">Control=20 Panel/Dashboard apps, pushing real-time monitoring data to the display. (= Biz=20 metrics, CPU/Memory usage etc )</SPAN></FONT>=20 <LI class=3DMsoNormal style=3D"COLOR: blue"><FONT face=3D"Bookman Old Sty= le"=20 color=3Dblue size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Bookman Old Style'">Multi-User=20 applications. Any time data is relevant to many parties. Example would be= ticketing application…customer service has application running 24/= 7 on their=20 desktop…ticket statuses are pushed to clients as they’re=20 updated.</SPAN></FONT>=20 <LI class=3DMsoNormal style=3D"COLOR: blue"><FONT face=3D"Bookman Old Sty= le"=20 color=3Dblue size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Bookman Old Style'">External R= 20;push” from=20 outside systems (as Steven mentioned). Let’s take the ticketing exa= mple once=20 again, ‘users’ are not the only way for tickets to enter the = system. We’d like=20 all our products/services/systems to tie into this system. Real-time=20 trouble-ticket creation. System A throws an exception which is caught and= in=20 turn ‘fed’ into system B in the form of a trouble ticket. (fl= ex enabled=20 ticketing system)</SPAN></FONT> </LI></OL> <P class=3DMsoNormal><FONT face=3D"Bookman Old Style" color=3Dblue size=3D2= ><SPAN=20 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Bookman Old Style'"></= SPAN></FONT> </P> <P class=3DMsoNormal><FONT face=3D"Bookman Old Style" color=3Dblue size=3D2= ><SPAN=20 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Bookman Old Style'">St= ace =20 :D</SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Bookman Old Style" color=3Dblue size=3D2= ><SPAN=20 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Bookman Old Style'"></= SPAN></FONT> </P> <DIV> <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT=20 face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt"> <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2> </SPAN></FONT></DIV> <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20 style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SP= AN></FONT></B><FONT=20 face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"= > Libby=20 Freligh [mailto:[EMAIL PROTECTED] <BR><B><SPAN=20 style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, April 05, 2004 2:43=20 PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20 [email protected]<BR><B><SPAN=20 style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [flexcoders] Flex Needs= Remote=20 Shared Objects!</SPAN></FONT></P></DIV> <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20 style=3D"FONT-SIZE: 12pt"></SPAN></FONT> </P> <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20 style=3D"FONT-SIZE: 12pt"></SPAN></FONT> </P> <DIV> <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Use cases,&= nbsp;friends, use cases!=20 It's definitely a feature we'll be investigating but I'd love to hear as ma= ny=20 specific use cases as possible.</SPAN></FONT></P></DIV> <DIV> <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20 style=3D"FONT-SIZE: 12pt"></SPAN></FONT> </P></DIV> <DIV> <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">l.=20 </SPAN></FONT></P></DIV> <DIV> <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20 style=3D"FONT-SIZE: 12pt"></SPAN></FONT> </P></DIV> <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT=20 face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt"> <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2> </SPAN></FONT></DIV> <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT face=3DTahoma s= ize=3D2><SPAN=20 style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SP= AN></FONT></B><FONT=20 face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"= > Steven=20 Webster [mailto:[EMAIL PROTECTED] <BR><B><SPAN=20 style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Sunday, April 04, 2004 1:57=20 AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20 [email protected]<BR><B><SPAN=20 style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [flexcoders] Flex Needs= Remote=20 Shared Objects!</SPAN></FONT></P> <P class=3DMsoNormal><TT><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt">On Sun, 2004-04-04 at 04:49, Stacy Young=20 wrote:</SPAN></FONT></TT><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"><BR><TT><FONT=20 face=3D"Courier New">> Here's a vote for a 1.x (one can hope) or a 2.x r= elease=20 of Flex. Add the</FONT></TT><BR><TT><FONT face=3D"Courier New">> ability= to=20 push data to clients. Essentially a subset of features</FONT></TT><BR><TT><= FONT=20 face=3D"Courier New">> offered by Flashcom...or more specifically, remot= e=20 shared objects. That</FONT></TT><BR><TT><FONT face=3D"Courier New">> wou= ld be=20 SO killer...and would close the book on benefits of RIAs in=20 the</FONT></TT><BR><TT><FONT face=3D"Courier New">> biz=20 world.</FONT></TT><BR><BR><TT><FONT face=3D"Courier New">I'll second this .= .. and=20 more importantly, the ability to drive</FONT></TT><BR><TT><FONT=20 face=3D"Courier New">the "push" from the server-side application (which Fla= sh=20 Comm</FONT></TT><BR><TT><FONT face=3D"Courier New">doesn't support=20 directly).</FONT></TT><BR><BR><TT><FONT face=3D"Courier New">I guess this i= s quite=20 a big ask though...</FONT></TT><BR><BR><TT><FONT=20 face=3D"Courier New">Steven</FONT></TT><BR><BR></SPAN></FONT><BR><BR></P><B= R></DIV><BR><FONT SIZE=3D3><BR> <BR> <table width=3D800 cellpadding=3D4 cellspacing=3D10 border=3D0><tr bgcolor= =3DBDBDBD><td valign=3Dtop width=3D400><font face=3Dverdana size=3D2 color= =3DFFFFFF><b>AVIS IMPORTANT</b></font></td><td valign=3Dtop width=3D400><fo= nt face=3Dverdana size=3D2 color=3DFFFFFF><b>WARNING</b></font></td></tr><t= r><td valign=3Dtop width=3D400><p align=3Djustify><font face=3Dverdana size= =3D1 color=3D808080> Les informations contenues dans le present document et= ses pieces jointes sont strictement confidentielles et reservees a l'usage= de la (des) personne(s) a qui il est adresse. Si vous n'etes pas le destin= ataire, soyez avise que toute divulgation, distribution, copie, ou autre ut= ilisation de ces informations est strictement prohibee. Si vous avez recu c= e document par erreur, veuillez s'il vous plait communiquer immediatement a= vec l'expediteur et detruire ce document sans en faire de copie sous quelqu= e forme.</td><td valign=3Dtop width=3D400><p align=3Djustify><font face=3Dv= erdana size=3D1 color=3D808080> The information contained in this document = and attachments is confidential and intended only for the person(s) named a= bove. If you are not the intended recipient you are hereby notified that an= y disclosure, copying, distribution, or any other use of the information is= strictly prohibited. If you have received this document by mistake, please= notify the sender immediately and destroy this document and attachments wi= thout making any copy of any kind.</td></tr></table><BR> </FONT> </BODY></HTML> ------_=_NextPart_001_01C41B53.511F8158--
