RE: [PHP-SOAP-DEV] New Release php-soap_0.1.1

[phpsurf <ph...@if...>]

by the way, like you added __getLastMessage() to get the last request send
by the client, can you also add a method to get the last response received
by the server ? something like __getLastResponse() or whatever you want :)

thx

> -----Original Message-----
> From: php...@li...
> [mailto:php...@li...]On Behalf
> Of brad lafountain
> Sent: jeudi 2 mai 2002 07:05
> To: php...@li...
> Cc: ahr...@ic...
> Subject: [PHP-SOAP-DEV] New Release php-soap_0.1.1
>
>
> Ok i have put out a new release.
> I know that that was quick.. I havn't added that much but i realized i did
> something that was't good. So i suggest who ever is using it use the new
> update.
>
> What this does...
>
> Some handing stuff..
> The server useto automatically send a fault when
> always_populate_raw_post_data
> was off. Now it will check for HTTP_RAW_POST_DATA first then check the ini
> setting and if it's off it will finally send the fault saying the
> ini setting
> should be on.
>
> The client useto deny any request that doesn't have the
> Content-Type: text/xml.
> I changed it so that it will check the header first if its not
> xml it will read
> the first 5 bytes and see if its xml ("<?xml"). If that is true
> it will try and
> process the request normall.
>
> By default the server automatically exposed all methods available
> to php. I
> changed it so that it doesn't expose any. You now will have to
> tell the server
> every function you want exposed.
> See...
> http://phpsoaptoolkit.sourceforge.net/phpsoap/guide/documentation/
classes/soapserver/addfunction/

You can still expose all methods by calling
$soap_server->addFunction(SOAP_FUNCTIONS_ALL);
but its not default anymore..

New Features..
On the server side you can now return custom faults..

function do_something($data)
{
 if(!$data)
   return new SoapFault(string "fault_string" [, string "fault_code"] [,
mixed
"details] [, "fault_actor]);

 return "thanks for suppling $data";
}

On the client side you can now see the seralized soap call

$client->some_soap_call();
echo $client->__getLastMessage();

The big reason for the patch already..
 I added php stream handling code for the upcomming streams in php-4.3.0.
When
i did i change php_close_socket(socket) to close(socket). So all of you
client
calls are keeping a connection to the server. So if you are calling multiple
calls to the same server you will notice a huge performance difference.

 And i fixed a few mem leaks.

 And the config.m4 file in the tar ball won't be a tar ball again.

 A windows binary and tarballs will be posted shortly

 Enjoy.. keep the feed back comming.

 -Brad


__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: ban...@so...
_______________________________________________
Phpsoaptoolkit-development mailing list
Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpsoaptoolkit-development

 
______________________________________________________________________________
ifrance.com, l'email gratuit le plus complet de l'Internet !
vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP...
http://www.ifrance.com/_reloc/email.emailif