Ok here I am....
I do already have some email lists up for my extension.
[EMAIL PROTECTED]
[EMAIL PROTECTED]
I've been doing ALOT of work with my extension. And i currently do use it live
at work. We have a java interface talking to "SoapObjects" on the server. This
is extremly powerfull cause it take advantage of php seralization and php
sessions to "persist" php-soap objects. So basicall you have a php-soap
application server that can commiuncate with any client. Run a php object in
any language that supports soap.
here are some snipplits that explain what im doing....
<?
$client = new SoapObject("http://serverendpoint.com/somescript.php";,
"urn:Test");
$client->setData("someData");
echo $client->getData();
$client->destroy();
?>
<?
$server = new SoapServer("urn:Test");
$server->setClass("myClass");
$server->setPersistence(SOAP_PERSISTENCE_SESSION);
$server->handle();
class myClass
{
var $data;
function setData($data)
{
$this->data = $data;
}
function getData()
{
return $this->data;
}
function destroy()
{
session_destroy();
}
}
?>
now with the above example you can see how you can have "persitiant" php
objects "running" on a remote server. I use this type of functionality in my
java gui. All of my database objects are writtin in php they do the data
extract. Then the java gui can fetch the data. Now if i don't like java i can
create php-gtk appliation use php-soap and i don't need to re-write my database
objects or MFC or VB etc etc. And now you can give this gui application to
customers and have them run it... and if you ever want to change your
underlaying db structure or any business logic you don't need to release a new
application you can control it thru your phpsoapobjects.
Since the "perstited" object is using php-session handling you can control
where the objects go. So i take it a step further i use msession to handle my
objects. Now i can have a "cluster" of php-soap application servers each soap
call "method call" can run on a different server or if you want pure speed you
can set up your session handling to use mod_mm but you don't have the whole
clustering part.
My extension is very young. it still needs alot of work but it also includes
alot of functionality.
the website is
http://phpsoaptoolkit.sourceforge.net/
- Brad
--- Dietrich Ayala <[EMAIL PROTECTED]> wrote:
> i'm under contract. i'd definitely contribute as much as possible on the list
> though :)
>
> i think these are excellent steps for PHP in this area. i get an amazing
> amount of NuSOAP-related email every day from developers
> who (for whatever reason) think that SOAP is the shiznit, and are creating
> all kinds of crazy web services. Most are trying to talk
> to other SOAP toolkits (mostly .NET & Apache).
>
> suggestions:
> 1. interop is key. get an endpoint up for brad's extension, and register it
> w/ soapbuilders list.
> 2. implement solid document-oriented messaging support (doc/lit) into brad's
> extension.
>
> dietrich
>
> > -----Original Message-----
> > From: Shane Caraveo [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 23, 2002 11:04 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [PHP-DEV] Re: [PEAR-DEV] SOAP, XMLRPC and WSDL
> >
> >
> >
> > I would be happy to lead the effort on the soap front. I've spoken a
> > bit with Brad about combining our efforts but got sidetracked over the
> > last couple weeks so haven't followed up on that. I'm also not sure
> > whether Deitrich is tied to NuSphere with his work, it'd be nice if we
> > could get him to work on this also (I'm sure he's lurking here ;).
> > There have been a couple others contacting me about working on the soap
> > stuff as well.
> >
> > Shane
> >
> > Rasmus Lerdorf wrote:
> >
> > pear/SOAP seems to work pretty well. There are few people out there that
> > know more about SOAP than Shane and I am quite comfortable having him
> > spearheading this effort. We can easily set up a php-soap mailing list if
> > enough people are interested.
> >
> > -Rasmus
> >
> > On Thu, 23 May 2002, Lukas Smith wrote:
> >
> >
> > > Yeah, I keep seeing PHP SOAP and XMLRPC being announce packages
> > > everywhere.
> > > But incompatible API's will not benefit PHP much and the efforts are
> > > simply redundant.
> > >
> > > I think it would make sense to create such a mailinglist.
> > > As I am still fairly busy with working on a merge of Metabase and PEAR
> > > DB called MDB (blatant plug :-) ) I can't spend as much time as I would
> > > wish on this topic.
> > >
> > > For now I will try to order the feedback I get and put together a little
> > > static page with the content.
> > >
> > > Basically I will take every package I find and list it there and put any
> > > comments people send regarding that package underneath.
> > >
> > > Best regards,
> > > Lukas Smith
> > > [EMAIL PROTECTED]
> >
> >
> > --
> > PHP Development Mailing List <http://www.php.net/>
> > To unsubscribe, visit: http://www.php.net/unsub.php
> >
> >
> >
>
>
> --
> PHP Development Mailing List <http://www.php.net/>
> To unsubscribe, visit: http://www.php.net/unsub.php
>
__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
