yeah, things definitely can get destroyed before they're done
instantiating. That's the purpose of the __LZdeleted flag. Another
possibility would be to just set this flag and not run destroy code until
node.initialize is done.

A

On Jun 2, P T Withington wrote:

> Henry and I are debugging replication in DHTML, and found an interesting
> effect:  When a node is initialized and is given a datapath it gets replaced
> by a replication manager when applyArgs happens.  If pooling is off, the
> replication manager will destroy the node, while it is still in
> node.initialize.  So it appears node.initialize needs to be prepared to exit
> early after apply args, otherwise it tries to continue initializing the node
> and trips over things, like LZinstantiationDone having been set to null by
> destroy.
_______________________________________________
Laszlo-dev mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-dev

Reply via email to