On 11/17/2010 5:06 PM, Christopher Browne wrote:
> A thing that several of us have been ruminating over for a while is the
> problem that people get confused about how you submit Slonik scripts,
> you may have some actions that require waits.

One major problem with automatic waiting for events is that it is 
extremely context sensitive to wait at all.

One cannot wait inside of a TRY block. The events aren't committed yet, 
so they cannot propagate.

One needs to be careful not to wait if the current path configuration is 
incomplete. You should for example never wait for the FIRST store path 
... you'd wait forever.

This all basically exposes that slonik has insufficient knowledge about 
the overall cluster configuration and healthiness. It basically fires 
off "commands" blindly. I've long been thinking that slonik itself needs 
a major overhaul. My recent experiences with the Mozilla Rhino 
JavaScript engine (Steve and I developed a cluster test framework using 
it) makes me think that actually creating a complete new slonik from 
scratch won't be too bad of an idea.


Jan

-- 
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin