Re: Race condition in Dancer

[Anonymous Monk]

in reply to Race condition in Dancer

Ah, classic rookie mistakes :) smell so good :)

Here is a tip , development.yml contains

# auto_reload is a development and experimental feature
# you should enable it by yourself if you want it
# Module::Refresh is needed 
# 
# Be aware it's unstable and may cause a memory leak.
# DO NOT EVER USE THIS FEATURE IN PRODUCTION 
# OR TINY KITTENS SHALL DIE WITH LOTS OF SUFFERING

If you saw that and said to yourself : I know how to fix it, I'll use Shotgun!

Don't! At least on win32 mingw perl v5.14.1, it works nicely to eat all memory :)

OTOH auto_reload: 1 does require manual restart after 3-6 edits , irritating :)

[Anonymous Monk]

plackup --loader Shotgun ...dancer

[choroba]

classic rookie mistakes

Is it a rookie mistake to believe the modules installed from CPAN? Or is the author of Dancer::Session::YAML a rookie?

[jmlynesjr]

I have wondered the same thing myself.

In a prior life when I was developing life/safety embedded systems in C there were several very attractive 3rd party C Libraries that would have saved a lot of time and effort. However, I could not justify the risk of using these packages. Yes, the C compiler also came from an outside vendor, but at least it was from a large company with deep pockets in case the lawyers ever got involved.

Maybe the CPAN modules you(all) use aren't life/safety related, but CEOs these days can be held criminally liable for failures in information systems(hacking/idenity theft/etc) and most can't evaluate their risk. At least a large user base should shake out problems quicker.

What say you?

James

[Anonymous Monk]

Is it a rookie mistake to believe the modules installed from CPAN? Or is the author of Dancer::Session::YAML a rookie?

IIRC every tutorial on locking/open I've seen warns you about clobbering your files, and before you obtain a lock -- the idiom is open without clobber, obtain lock, trunc/seek/write as needed, close