entropyreduction wrote: > Before I put time in to plugin, I gotta know have some rationale for > putting that functionality into Powerpro. What can you get out of a > Powerpro plugin that you can;t achieve using command-line ftp, driven > by Powerpro script? >
david wrote: >> It's the network extension that powerpro has never had. I'm jumping into the middle of a discussion that I haven't followed, but my sense is that pretty much any network function could be achieved via an external utility driven by powerpro, including pop3, icmp, etc. which however found a way into becoming plugins. So the argument goes that there isn't a good rationale for writing net plugins. However, driving an external utility by means of powerpro is almost always a matter of adjusting wait.for or sendkey or whatever for one's particular system, before it works. So the counterpoint I see is what network functionality do you want to "standardize" into a plugin so that it works out-of-the-box for all systems. I'm not sure that that can be achieved, but it is one way to look for a rationale. Personally I don't use the net or pop3 plugins, although I make intensive use of pop3, ftp, ping, http, because I found external utilities that work well for me. I wouldn't dare sharing my solutions with others, because they're very customized. Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
