START OF CALL: 2004-09-22 END OF CALL: 2004-09-27
Accept the new multicast/unicast code: [X] -1 (NO), because :
No I don't accept the code as is , since by removing the spawn per message it will break when a message gets handled incorrectly. When an exception occurs for a local message, future messages both local and remote won't be handled. Also there is no control or handling of messages that go into never-never land (or take a *long* time). In that case changes may be handled seconds, minutes or hours after arriving, causing strange effects.
Moving the code to org.mmbase.storage .shared : [X] -1 (NO), because : Name does not reflect the function.
-- Rico Jansen ([EMAIL PROTECTED]) "You call it untidy, I call it LRU ordered" -- Daniel Barlow
