Re: [Axis2] PHP XML IN-OUT Message Receiver

[Nabeel Yoosuf]

IMHO, Ideally this should be kept in a location independent of both PHP and Axis2/C repos. If a user wants to have PHP web services in C, (s)he needs to first download PHP and Axis2/C. Then  download and compile the receiver using the downloaded PHP and Axis2/C libraries. Since,  neither PHP nor Axis2/C is dependent on this receiver; it just uses what is provided by them.

We can find reason for and againts keeping custom receivers in Axis2 repo. I wonder how Axis2 java guys keep custom receivers? What if I write a C++ message receiver?

-Nabeel

On 6/4/06, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:

I think it is better if we keep it in a PHP related repo.
It is the PHP code that is based on Axis2/C, not that Axis2/C depends on
PHP. Hence it is the responsibility of the PHP module to hold this code
IMHO.

Thanks,
Samisa...

Nabeel Yoosuf wrote:

> PHP XML IN-OUT Message Receiver
> -------------------------------------------------------
>
> This message receiver allows you to write your web services
> implementation in PHP and expose it through Axis2/C engine.
>
> It uses PHP embed SAPI to call PHP code from C.
>
> The README file gives some details about the receiver and how to
> install it.
>
> There are two examples shipped with this. echo and math services. Drop
> them into services folder and you can call it from any client!
>
> I think this should go to a folder called "contributions" inside
> Axis2/C SVN. (c/contributions/php_xml_msg_recv/)
>
> -Nabeel
>
>------------------------------------------------------------------------
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]