Storable Stream - Module namespace help
Hello, In need for a way to transfer a large amount of small datastructures I created a module that stores and retrieves a stream of storables in a file. I created it in a private Namespace using in the company I worked for but, with they permission, and because I think this may be useful for someone else, I want to publish it on cpan. I'm finishing documentation and tests, before uploading it to CPAN, but I don't know exactly which namespace to use. For me, the obvious namespace would be Storable::Stream (and eventually Storable::Stream::GZip), but as Storable is part of core, I think we are not expected to publish modules in that namespace. So, which name should I use for this small module? Thanks, mpneves -- Magick Source http://www.magick-source.net -- Magick Source http://www.magick-source.net
Re: The CPAN Definitive Tags Spec
* Shlomi Fish shlo...@iglu.org.il [2010-08-07 15:15]: There's an easy solution to this problem - have this tag retire after there hasn't been a new release in, say, 6 months. Or maybe we can call it something else. (By retire I mean that search engines, indexers, raters, etc. will ignore it, not that it will be physically removed from the META.yml). * Ovid publiustemp-moduleautho...@yahoo.com [2010-08-07 15:01]: On a related note, I've not made a new release of Sub::Override in 5 years because it's complete and apparently correct. Is it actively developed or not? Maybe I wasn't clear enough in the SPEC, but it wouldn't be def/active_dev because it's not constantly enhanced. What I meant by active_dev is that the module is constantly enhanced / expanded / etc. Oh ho. Shlomi, meet Mark Jason. Mark, meet Shlomi. http://perl.plover.com/yak/12views/samples/notes.html#sl-9 Regards, -- Aristotle Pagaltzis // http://plasmasturm.org/
Re: Storable Stream - Module namespace help
* Marco Neves [ModAuthors] perl-module-auth...@knowhunter.cjb.net [2010-08-08
12:00]:
So, which name should I use for this small module?
First thing that popped into my head was Archive::Storable.
Now I can’t decide whether it’s perfect or silly.
--
*AUTOLOAD=*_;sub _{s/::([^:]*)$/print$1,(,$\/, )[defined
wantarray]/e;chop;$_}
Just-another-Perl-hack;
#Aristotle Pagaltzis // http://plasmasturm.org/
Re: The CPAN Definitive Tags Spec
Hi Aristotle, On Sunday 08 August 2010 15:35:33 Aristotle Pagaltzis wrote: * Shlomi Fish shlo...@iglu.org.il [2010-08-07 15:15]: There's an easy solution to this problem - have this tag retire after there hasn't been a new release in, say, 6 months. Or maybe we can call it something else. (By retire I mean that search engines, indexers, raters, etc. will ignore it, not that it will be physically removed from the META.yml). * Ovid publiustemp-moduleautho...@yahoo.com [2010-08-07 15:01]: On a related note, I've not made a new release of Sub::Override in 5 years because it's complete and apparently correct. Is it actively developed or not? Maybe I wasn't clear enough in the SPEC, but it wouldn't be def/active_dev because it's not constantly enhanced. What I meant by active_dev is that the module is constantly enhanced / expanded / etc. Oh ho. Shlomi, meet Mark Jason. Mark, meet Shlomi. http://perl.plover.com/yak/12views/samples/notes.html#sl-9 Yes, I'm familiar with what MJD says there (and even attended the original presentation that he gave at the first YAPC::Israel). I didn't intend the lack of active_dev and the fact that a module is complete and has a stable and non-expanding API to be an indication of being somehow bad. By all means active_dev is an indication that the author of the module still has some idea for enhancements (read - not bug fixes or internals cleanup) in the queue, and that you should expect more from him. I didn't mean to imply that a module with a stable API has been abandoned or is not recommended. Regards, Shlomi Fish -- - Shlomi Fish http://www.shlomifish.org/ First stop for Perl beginners - http://perl-begin.org/ God considered inflicting XSLT as the tenth plague of Egypt, but then decided against it because he thought it would be too evil. Please reply to list if it's a mailing list post - http://shlom.in/reply .
Re: The CPAN Definitive Tags Spec
On Sun, Aug 8, 2010 at 9:04 AM, Shlomi Fish shlo...@iglu.org.il wrote: By all means active_dev is an indication that the author of the module still has some idea for enhancements (read - not bug fixes or internals cleanup) in the queue, and that you should expect more from him. Maybe wip or the more verbosely work_in_progress would state that more clearly? *Corwin* 612-217-1742 612-298-0615 (fax) 612-695-4276 (mobile) *cor...@mpls.cx*
Storable Stream - Module namespace help
Hello, In need for a way to transfer a large amount of small datastructures I created a module that stores and retrieves a stream of storables in a file. I created it in a private Namespace using in the company I worked for but, with they permission, and because I think this may be useful for someone else, I want to publish it on cpan. I'm finishing documentation and tests, before uploading it to CPAN, but I don't know exactly which namespace to use. For me, the obvious namespace would be Storable::Stream (and eventually Storable::Stream::GZip), but as Storable is part of core, I think we are not expected to publish modules in that namespace. So, which name should I use for this small module? Thanks, mpneves -- Magick Source http://www.magick-source.net
Re: Storable Stream - Module namespace help
On Sun, Aug 8, 2010 at 2:40 AM, theMage [Marco Neves] perl-c...@knowhunter.cjb.net wrote: Hello, In need for a way to transfer a large amount of small datastructures I created a module that stores and retrieves a stream of storables in a file. I created it in a private Namespace using in the company I worked for but, with they permission, and because I think this may be useful for someone else, I want to publish it on cpan. I'm finishing documentation and tests, before uploading it to CPAN, but I don't know exactly which namespace to use. For me, the obvious namespace would be Storable::Stream (and eventually Storable::Stream::GZip), but as Storable is part of core, I think we are not expected to publish modules in that namespace. So, which name should I use for this small module? The namespace ought to be just fine. The package Storable is owned by core but Storable::Stream isn't. FWIW though, I am provoked by SO MUCH PAIN transferring Storable objects between processes and servers that I feel like I must warn you against ever actually using Storable in IPC. I've had so many problems when one of either client or server for Storable-trading IPC wanted to change. Have you tried upgrading or downgrading either side of the transaction to a new, potentially incompatible version of Storable yet? I'd feel much better suggesting you consider streaming with YAML or JSON or something hand-rolled but anything but Storable. Consider that maybe your next client will want to be implemented in Ruby but now won't be able to read the data. BTW, where's your repo? github? I'd like to take a gander. Josh
