> > The hack doesn't remove the multicast. It offers an alternative
> > implementation (unicast). This gives people a choice.
>
> Hmm. Ok, went a bit deeper int he code, and maybe not...
> Must have misunderstood. This multicast code is almost
> incomprehensible, and almost impossible to determine when
> which spawns what.
Old system
MMBaseMulticast
start thread and read network and put into receivequeue
MulticastChangesReceiver (started by MMBaseMulticast)
start thread and write to network from sendqueue
MulticastChangesReceiver (started by MMBaseMulticast)
start thread and read from receivequeue. Spawn
MMBaseMulticastProbe-thread for every message
Handling message code in MMBaseMulticast is used by this thread
(Makes it very confusing)
My Hack
MMBaseSharedStorage (MMBaseMulticast)
start thread and read from receivequeue. Spawn
MMBaseMulticastProbe-thread for every message (was replaced in hack by
nodeChanged method)
MulticastChangesReceiver (started by MMBaseMulticast)
start thread and write to network from sendqueue
MulticastChangesReceiver (started by MMBaseMulticast)
start thread and read network and put into receivequeue
If you compare old MMBaseMulticast with hack MMBaseSharedStorage then there
are not a lot of diffeneces. Only Multicast specific stuff is missing and
identation is different.
Nico
