> -----Oorspronkelijk bericht----- > Van: Michiel Meeuwissen [mailto:[EMAIL PROTECTED] > Verzonden: dinsdag 20 april 2004 13:17 > Aan: [EMAIL PROTECTED] > Onderwerp: Re: MMBase MultiCast errors > > > Andr? van Toly <[EMAIL PROTECTED]> wrote: > > >That is probably because that Multicast spawns a thread > for every node > > >change received. So when you are doing lots of node changes it gets > > >bogged down. > > > > My point exactly: When you save a complicated > > EditWizard (f.e. a news wizard with related > > images, urls, mediasources etc.) all nodes that > > were opened in the wizard are considered changed > > and will be multicasted over all the MMBase > > instances that share the same cloud. Resulting in > > a huge number of Multicast threads etc. > > > There are more problems with multicast: > > - IIRC a multicast is not garanteed to be received > > - multicast can only be done within the same subnet, while > this is not true > for the database connection. So, if you run 2 mmbase's on > the same database, > but in a different network, multicast cannot be used to > synchronize the > caches. > > So, perhaps there needs to be a small project who offers an > alternative for > multicast. Perhaps using RMI or so. It should then of course > also consider > this Thread issue. > how about a event table in the database? that is definitly a shared resource. different instances could keep a watch on the table (one thread), and process all events.
ernst > > Michiel > > > > -- > Michiel Meeuwissen | > Mediapark C101 Hilversum | > +31 (0)35 6772979 | I hate computers > nl_NL eo_XX en_US | > mihxil' | > [] () | >
