I understand this is supposed to be a joke and/or political comment, but I don't think it's particularly successful as either.
1 out of 1 found this review helpful. Was this review helpful to you? Yes No
We have used this module for several months to manage a stream of video encoding jobs submitted by multiple servers to be processed on another. The queue directory is mounted over NFS and all of the inter-process communication and locking seems to work reliably.
11 out of 11 found this review helpful. Was this review helpful to you? Yes No
A clean and simple interface to a high-speed shared cache system.
4 out of 5 found this review helpful. Was this review helpful to you? Yes No
It was easy to integrate this into an HTML::Mason site and we were able to use it to build a new AJAX-based feature on our first day without worrying about the usual browser dependencies. I'll be reaching for this regularly...
8 out of 9 found this review helpful. Was this review helpful to you? Yes No
Sorting may seem "simple," and sometimes it is. But when you need to be able to dynamically sort things in unexpected ways and still be reasonably fast for non-trivial data sets, the complexity mounts. Scattering sort optimization logic in a dozen places throughout your application is a maintance nightmare. That's when you realize you need Sort::Maker.
I encountered this same need years ago, before Sort::Maker had been published, and ended up writing the Data::Sorting module, which uses many of the same techniques, but for future applications I think I'll reach for Sort::Maker first.
6 out of 6 found this review helpful. Was this review helpful to you? Yes No
Hi, a quick response from the author of Class::MakeMethods to the earlier comment on this distribution: The organization and clarity of the documentation is a known problem with which I continue to struggle. Class::MakeMethods provides a big matrix of method types that differ in various minor ways, and it's hard for me to see how to best present those choices to the new user. (The top item in the ToDo file is "Make sure that the documentation is broken up into appropriately-sized chunks, and that people will know which section to look at.")
While it's nice to hear that others are "willing to help if necessary" I'm not sure how to interpret "necessary." I've already spent some "serious time" trying to improve the documentation, with mixed results. The few documentation patches that I've received have all been incorporated. If anyone else is willing to help improve the documentation, their help would be warmly appreciated. (The ReadMe specifically states that "I would be particularly interested in any suggestions towards improving the documentation...") Patches, new documents, suggestions, or specific complaints through any of the typical feedback channels would all be welcome. Thanks!
2 out of 2 found this review helpful. Was this review helpful to you? Yes No
Excellent tool; a valuable assistance to module authors in improving their tests. Documentation may seem a bit skimpy, but if you just install and run it, the reports it produces are mostly self-explanatory.
4 out of 4 found this review helpful. Was this review helpful to you? Yes No