Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:14047 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13198 invoked by uid 1010); 11 Dec 2004 14:46:56 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 13016 invoked by uid 1007); 11 Dec 2004 14:46:55 -0000 Message-ID: <20041211144655.12998.qmail@pb1.pair.com> To: internals@lists.php.net Date: Sat, 11 Dec 2004 15:46:44 +0100 Lines: 18 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Posted-By: 212.238.144.71 Subject: throwing exceptions through SOAP From: r.korving@xit.nl ("Ron Korving") Hi, I think it would be a pretty nice feature if a SOAP function could throw an exception which would be caught on the client side of the connection without the server script stopping when the SOAP server was made persistent. This would make it much more suitable for commandline php5-scripts with SOAP. I've spoken with Dmitry Stogov about this quite a while ago (when php5.0 was still in beta), and he thought it would turn out to be very difficult to implement. Still, I consider this very desired behaviour, so I figured I'd mention it here in the internals. Who knows, maybe somebody feels the urge to fix this issue :) Thanks, Ron Korving