> From: y2k_sonu <[EMAIL PROTECTED]>
> Subject: [twincling] Perl web service implemetation Query.
> Sent: 13 Mar '07 11:17
>
> Hi All,
>
> I want suggestions for my problem.
>
> I have a machine (A) which has an IIS sever with php implementation.
> This PHP implementation upload file from user's location, copy it to
> Machine `A' & run some Commands there, process the file, if successful
> then give user a FTP link to download it.
>
> There is one other machine (B) which has some files.
> I want to run a Perl script on machine `B' & get file Processed from
> Machine `A'.
> Processing can happen on Machine `A' only.
> Script has to copy file to machine `A' run some command (on Machine A)
> process the file & if successful then copy file back to Machine B.
>
> Both machines are on network.
>
> What should I do for this?
Hi Sumit:
There are two parts to this -
1. server side
this is where the service will be made available for the various operations
2. client
you are running a PERL script here and so your interaction with the server
will be through the script code.
There are three possibilities here -
1. sockets
2. RPC
3. webservice
Webservice will be a good option -
. service will be available over HTTP transport and firewall friendly.
. client code will require addition of an extra function in the code path,
send_n_process();
. both PHP and PERL have webservice toolkits and given usage of XML, they
will be both
platform and language agnostic.
. PHP webservice can be hosted off IIS potentially (you need to check that).
Sockets and RPC are more hardwork, since you need to either devise a protocol
for your communication
or work with XADDR stuff (RPC). Webservices leveraged on HTTP protocol and
webserver/app servers
solve the same problem more elegantly.
These are just my thoughts. Other members may want to pitch in their
experiences/thoughts.
thanks
Saifi.
