Re: How to serialize Net::FTP object?

It's very likely impossible to serialize a Net::FTP object.

There is an easier solution for your problem, though. Put the code that uses the FTP object in a subroutine (in a module, or in the same file as the code that creates the object) and call that sub.

If that's impossible (because of the structure of the other script), you can put the object in a global and do the script.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Comment on Re: How to serialize Net::FTP object? Download Code

Replies are listed 'Best First'.
Re^2: How to serialize Net::FTP object? by redss (Monk) on Dec 06, 2004 at 21:56 UTC
Thanks for your reply. The problem is since the first script creates the FTP object, and the other script (which uses the FTP object) would be invoked by an external process, there is no way to merge the 2 scripts. It would be 2 separate invocations, unless there is a way for the 2nd script to send a message to the first script. Here is my application: I want my text editor to invoke a program to ftp a file to a remote host when I need it to, but I want the ftp connection to already be open so that the text editor only needs to send the file, instead of initializing the connection each time. Ideas?	[reply]
Re^3: How to serialize Net::FTP object? by BUU (Prior) on Dec 07, 2004 at 07:04 UTC
You can't pass the FTP object in any meaningful way. Your only option is to run a perl server locally that maintains the ftp connect and listens for some other type of connections. Then your text editor can talk to that server and that server can use the ftp connection. It will be faster than opening a ftp connection every time, mostly.	[reply]