RE: [flexcoders] Do I *REALLY* need Flex Data Services for WebServices?
Thanks all. It looks like I'll have to dig more under the covers of Flex / WS than I was expecting to. Thanks again. Greg. Greg McCreath Chief Technical Officer TAFMO Limited ABN: 94 109 766 592 Level 8, 342 Flinders Street Melbourne Victoria, 3000 Australia http://www.tafmo.com Ph : +61 (0) 3 9018 6824 Fax : +61 (0) 3 9018 6899 Mobile : +61 (0) 401 988 957 _ From: greg h [mailto:[EMAIL PROTECTED] Sent: Tuesday, 30 January 2007 5:01 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Do I *REALLY* need Flex Data Services for WebServices? Hi Greg, Regarding FDS pricing, there also is the FREE (as in FREE) Flex Data Services Express version. A quote below regarding FDS Express is pulled from the posting over at FlexAussie at this link: http://tech.groups.yahoo.com/group/flexaussie/message/158 http://tech.groups.yahoo.com/group/flexaussie/message/158 FDS Express does not have any connection limitations. With FDS Express you can run no more 1 CPU per application (this allows multiple applications per CPU) with no connection limitations. As your application requires more than 1 CPU for reliability or scalability we have a mid-level FDS offering. Another option may be using ColdFusion, which since version 7.0.2 supports a subset of FDS functionality. I would need to test to confirm that Proxying is included. hth, g On 1/28/07, Greg McCreath [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi All, The manual says: Note: You must use the Flex proxy, which is part of Flex Data Services, to ensure that HTTP status codes are returned correctly from HTTP services and web services. On web browsers, when a service returns any status code other than 200, Adobe Flash Player cannot read the body of the response. If the status code is 500 and the body contains a fault, there is no way to get to the fault. The proxy works around this issue by forcing the status code for faults to 200; the player passes the body of the response along with the fault intact. At US $6000 a pop per CPU (departmental license only - $20,000 per CPU for enterprise license) across multiple high-availability data centers you'd be looking down the barrel at more than US $50,000 ** to run a web service proxy ** on a number of good machines. So, does this effectively render Flex RPC services un-useable unless you use Flex Data Services? .. unless you make the assumption that everything always works ... .. what happens when a non-200 status code is encountered? ... or have I got it wrong ... ?? Greg. _ This email and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. This email may contain personal information of individuals, and be subject to Commonwealth and/or State privacy laws in Australia. This email is also subject to copyright. If you are not the intended recipient, you must not read, print, store, copy, forward or use this email for any reason, in accordance with privacy and copyright laws. If you have received this email in error, please notify the sender by return email, and delete this email from your inbox.
Re: [flexcoders] Do I *REALLY* need Flex Data Services for WebServices?
On Monday 29 January 2007 01:30, Greg McCreath wrote: So, does this effectively render Flex RPC services un-useable unless you use Flex Data Services? .. unless you make the assumption that everything always works ... You can still try/catch the execution, or make sure your results parser functions OK. -- Tom Chiverton Helping to ambassadorially maximize internet appliances This email is sent for and on behalf of Halliwells LLP. Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at St James's Court Brown Street Manchester M2 2JF. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by the Law Society. CONFIDENTIALITY This email is intended only for the use of the addressee named above and may be confidential or legally privileged. If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents. If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 8008. For more information about Halliwells LLP visit www.halliwells.com. -- 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 * To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ * Your email settings: Individual Email | Traditional * To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) * To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] * Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
Re: [flexcoders] Do I *REALLY* need Flex Data Services for WebServices?
Hi, I'm using WebService from a PHP server. It's working well except for fault that return a 500 code status. In PHP if you want to generate a fault you can use the SOAPFault that return a 500 code status with the error code and the error message. If there is fault in your PHP code, the SOAPFault is used. The flash player can't read the 500 code message because theses message are ignored. So nothing happen when an 500 code is sent. For myself, I use another tools to see the 500 error message if nothing happen in flash player. Is this answers your question ? Mickael Greg McCreath a écrit : Hi All, The manual says: Note: “You must use the Flex proxy, which is part of Flex Data Services, to ensure that HTTP status codes are returned correctly from HTTP services and web services. On web browsers, when a service returns any status code other than 200, Adobe Flash Player cannot read the body of the response. If the status code is 500 and the body contains a fault, there is no way to get to the fault. The proxy works around this issue by forcing the status code for faults to 200; the player passes the body of the response along with the fault intact.” At US $6000 a pop per CPU (departmental license only – $20,000 per CPU for enterprise license) across multiple high-availability data centers you’d be looking down the barrel at more than US $50,000 ** to run a web service proxy ** on a number of good machines. So, does this effectively render Flex RPC services un-useable unless you use Flex Data Services? .. unless you make the assumption that everything always works … .. what happens when a non-200 status code is encountered? … or have I got it wrong … ?? Greg. This email and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. This email may contain personal information of individuals, and be subject to Commonwealth and/or State privacy laws in Australia. This email is also subject to copyright. If you are not the intended recipient, you must not read, print, store, copy, forward or use this email for any reason, in accordance with privacy and copyright laws. If you have received this email in error, please notify the sender by return email, and delete this email from your inbox. begin:vcard fn:RUELLAN Mickael n:Mickael;RUELLAN adr;quoted-printable;dom:;;3 impasse lafargue;St Germain de la rivi=C3=A8re;;33240 email;internet:[EMAIL PROTECTED] tel;cell:0682342201 version:2.1 end:vcard
RE: [flexcoders] Do I *REALLY* need Flex Data Services for WebServices?
Status codes higher than 300 are not provided to Flash Player by the browser. It is an artifact of the inconsistencies within the plug-in API on certain browsers. The decision was made by the Flash Player team to keep the runtime behavior of the player consistent so there is no data provided when a 400, 404, 500 error occurs. This is why the proxy was created in the first place. The proxy changes the header error codes and returns them to the Flash Player in a suitable manner. Since Adobe could not force the browser manufacturers to change to return 300 or higher errors, we created a proxy to allow Web Services to work seamlessly. You can write your own Web Services Proxy and modify the results returned. Although if you go this route, you might as well use remoting to return an object to the player. The SOAP Web Services parser is very slow client side because of the nature of the work that it is doing. The performance decays exponentially with larger SOAP result objects and there are many encoding types that are not supported. Here are some sample stacks: FlexApp AMF Server WSSOAP Server -- 100% compatible, AMF exchange about 10X faster client to server. FlexApp WSSOAP Server -- 500 error issues If only Flash Player got 300 or higher status codes consistently from the various browsers. I wish it was a switch we could change but it isn't. Many point to this as Adobe pushing an expensive server but the reality is that we were trying to solve a problem and enable SOAP WS compatibility with the Proxy. We need a better solution in the WS-SOAP compatibility. Ted Patrick Flex Technical Evangelist Adobe Systems http://www.onflex.org http://www.onflex.org http://www.linkedin.com/in/tedpatrick http://www.linkedin.com/in/tedpatrick From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Greg McCreath Sent: Sunday, January 28, 2007 5:31 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Do I *REALLY* need Flex Data Services for WebServices? Hi All, The manual says: Note: You must use the Flex proxy, which is part of Flex Data Services, to ensure that HTTP status codes are returned correctly from HTTP services and web services. On web browsers, when a service returns any status code other than 200, Adobe Flash Player cannot read the body of the response. If the status code is 500 and the body contains a fault, there is no way to get to the fault. The proxy works around this issue by forcing the status code for faults to 200; the player passes the body of the response along with the fault intact. At US $6000 a pop per CPU (departmental license only - $20,000 per CPU for enterprise license) across multiple high-availability data centers you'd be looking down the barrel at more than US $50,000 ** to run a web service proxy ** on a number of good machines. So, does this effectively render Flex RPC services un-useable unless you use Flex Data Services? .. unless you make the assumption that everything always works ... .. what happens when a non-200 status code is encountered? ... or have I got it wrong ... ?? Greg. This email and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. This email may contain personal information of individuals, and be subject to Commonwealth and/or State privacy laws in Australia. This email is also subject to copyright. If you are not the intended recipient, you must not read, print, store, copy, forward or use this email for any reason, in accordance with privacy and copyright laws. If you have received this email in error, please notify the sender by return email, and delete this email from your inbox.
Re: [flexcoders] Do I *REALLY* need Flex Data Services for WebServices?
Hi Greg, Regarding FDS pricing, there also is the FREE (as in FREE) Flex Data Services Express version. A quote below regarding FDS Express is pulled from the posting over at FlexAussie at this link: http://tech.groups.yahoo.com/group/flexaussie/message/158 FDS Express does not have any connection limitations. With FDS Express you can run no more 1 CPU per application (this allows multiple applications per CPU) with no connection limitations. As your application requires more than 1 CPU for reliability or scalability we have a mid-level FDS offering. Another option may be using ColdFusion, which since version 7.0.2 supports a subset of FDS functionality. I would need to test to confirm that Proxying is included. hth, g On 1/28/07, Greg McCreath [EMAIL PROTECTED] wrote: Hi All, The manual says: Note: You must use the Flex proxy, which is part of Flex Data Services, to ensure that HTTP status codes are returned correctly from HTTP services and web services. On web browsers, when a service returns any status code other than 200, Adobe Flash Player cannot read the body of the response. If the status code is 500 and the body contains a fault, there is no way to get to the fault. The proxy works around this issue by forcing the status code for faults to 200; the player passes the body of the response along with the fault intact. At US $6000 a pop per CPU (departmental license only – $20,000 per CPU for enterprise license) across multiple high-availability data centers you'd be looking down the barrel at more than US $50,000 ** to run a web service proxy ** on a number of good machines. So, does this effectively render Flex RPC services un-useable unless you use Flex Data Services? .. unless you make the assumption that everything always works … .. what happens when a non-200 status code is encountered? … or have I got it wrong … ?? Greg. --
RE: [flexcoders] Do I *REALLY* need Flex Data Services for WebServices?
Don't let the price of FDS scare you if your core question is simply, Do I need FDS to use Webservices in Flex? Then the answer is no. Jason Merrill Bank of America Learning Organizational Effectiveness
