You also may want to take a look at POE::Component::DirWatch and POE::Component::DirWatch::Object as a way to trigger the start of the process.
1. FIle created by server --- Watcher on win32 discovers it 2. Watcher triggers the process action and generates result files 3. watcher on unix discovers results and does something with them Beware though that maybe im just eager for someone to use my module. (DirWatch::Object) groditi On 8/22/06, Jeff McCarrell <[EMAIL PROTECTED]> wrote:
Hi folks. I need to create a system that - moves some files generated on a *nix system to a win32 system - does some processing on those files - moves the results back to the *nix system The win32 system is the server side of the connection, and it needs to be able to support multiple clients, be highly available, etc. All of the usual daemon reqs, except for security. This is running inside the firewall, so I don't have to worry about that class of problems. My thought is to use POE and some of the FTP modules to handle the file transfers for a couple of reasons: - I don't want to deal with \r\n <-> \n line ending conversions - the result files are not text files My first thought was that POE and, in particular, POE::Component::Client::FTP and POE::Component::Server::FTP, were perfect matches, but the comments at http://poe.perl.org/?POE_Components_List are not inspiring to say the least. I could fall back to using Net::FTP and Net::FTPServer, I think, but that would make my client and server pretty chunky, and not very cooperative-multitasking-friendly. I've been through most all of the POE tutorials and docs, and I have the control protocol that I want the client and server to talk worked out pretty well. But I'm unclear on how best to leverage the POE and FTP combination. So I seek your wisdom: if it were your decision, which would you choose? Thanks in advance... -- jeff
