| Jose Nyimi 2005-03-29, 3:56 pm |
|
> -----Message d'origine-----
> De=A0: Peter Rabbitson [mailto:rabbit@rabbit.us]
> Envoy=E9=A0: mardi 29 mars 2005 12:05
> =C0=A0: beginners@perl.org
> Objet=A0: simple server app
>=20
> 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).
>=20
> Thank you
>=20
> Peter
>=20
Net::EasyTCP is an other alternative ...
http://search.cpan.org/~mnaguib/EasyTCP-0.26
BR,
Jos=E9.
|