I've decoupled POE::Pipe classes from POE, and I'll release them as IO::Pipely soon. I've created a new project repository for IO::Pipely here: https://github.com/rcaputo/io-pipely
This begins a long-term deprecation of the POE::Pipe classes. The plan so far: 0. Tell everyone about the upcoming POE::Pipe deprecation. You're reading it now. 1. Solicit feedback on IO::Pipely before the release. Please take a look and suggest refinements? "Check." 2. Release IO::Pipely. 3. Tell everyone they should migrate their POE::Pipe use to IO::Pipely ASAP. 4. Time passes. 5. Document POE::Pipe deprecation. 6. Make IO::Pipely a POE dependency. 7. Replace POE::Pipe guts with IO::Pipely calls. 8. Time passes. 9. Replace POE::Pipe usage in POE's core and tests with direct IO::Pipely usage. A. Remind people POE::Pipe is deprecated. B. Time passes. C. Remove POE::Pipe from POE's repository and distribution. D. Profit? Generally "time passes" is one or two POE releases. This can represent several months of real time depending on the frequency of bug reports (very low right now). Sorry in advance for breaking things. Hopefully it's far enough in the future so everyone can avoid problems. -- Rocco Caputo <rcap...@pobox.com>
