Yeah, the code I showed in an earlier message shows that Adobe have a try catch already which is supposed to then raise the Fault Event so us putting a try catch round their try catch would achieve nothing.
This whole issue is about Adobe raising an event in a catch block and that the Adobe code uses an object with holding a ref to it. --- In [email protected], Tom Chiverton <[EMAIL PROTECTED]> wrote: > > On Monday 06 Oct 2008, reflexactions wrote: > > So for us server fault are just great but client fault are the > > issue... > > Did you mention why you can't put your send() method inside a try/catch ? > > -- > Tom Chiverton > Helping to proactively architect customized web-enabled initiatives > > > > **************************************************** > > 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 Halliwells LLP, 3 Hardman Square, Spinningfields, Manchester, M3 3EB. 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 Solicitors Regulation Authority. > > 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 2500. > > For more information about Halliwells LLP visit www.halliwells.com. >
