"Peter Rabbitson" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi everyone, Here is my situation. I have a windows system which continuosly > runs a perl script, which utilizing Win32::Process and Win32::Setupsup is > controlling a windows only app and when triggered makes it spit export files > to a samba network share. From there on my main process which runs off a CGI > under linux uses those files for internal purposes and so on and so forth. I > would like to be able to trigger all exports remotely from the linux > machine. In order to do this I need to communicate 4 strings to the process > running on the windows machine. No information should be returned back, > except maybe a 0/1 flag signifying failure/completion. I looked into SOAP > and since I am not running Apache or IIS or anything else on the windows box > for increased stability I started thinking about something like > SOAP::Transport::TCP (not much docs to look at unfortunately). It seems to > be able to do the job, however I feel it is an overkill for communicating 4 > strings one way and 1 string the other way... I would appreciate if more > seasoned programmers share suggestions on how would they approach such a > problem (maybe there is something way simpler than SOAP that I simply do not > know about). >
In line with the SOAP approach, theres RPC-XML, a subset of SOAP. Its light weight and would be easy to implement your specs in this method: http://search.cpan.org/~rjray/RPC-XML-0.57/ It has a built in server called RPC::XML::Server. Theres also a RPC-XML server that comes with SOAP-Lite. The difference between the two is the way you define your network enabled functions. If you need a book, try _Programming Web Services with Perl_ excellently written and easy to read. Todd W. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
