comment on

"mainstream" was probably the wrong word to use. As I stated up front, I'm looking for best practices. It probably would have been more accurate for me to state at that it doesn't appear that there are very many best practices for this, which surprises me because it seemed to me like something common enough that it would have a recommended design pattern (at least in Perl)...

To your point, I very well may have to go with something a little off the beaten path in order to achieve what's needed for this project. That's probably going to be just fine. I was somewhat hopeful that there were some more established guidelines and how to go about this, given that it felt like a kind of common need.

Instead, I'm saying a lot of potentially great options, which isn't so bad! :-)

Tommy
A mistake can be valuable or costly, depending on how faithfully you pursue correction

In reply to Re^4: Polling a file for changes - Best Practices? by Tommy
in thread Polling a file for changes - Best Practices? by Tommy

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks