Do these cluster across processors or is it a single machine thing? The registration process would need to be cached to keep mapping speed up. It would be also interesting to see how the dieing daemon gracefully departs from the cache or map routing mechanism. As high volumes occur the mapper would be a bottle neck unless there are multiple instances of this portion as well. Just my thoughts I could be right off base though having not seen the whole nanite design.
Steve On Wed, Oct 15, 2008 at 3:16 AM, mdipierro <[EMAIL PROTECTED]> wrote: > > Not quite a normal appliance but it should be not difficult to clone > if people see a value in it. > > On Oct 14, 7:58 am, voltron <[EMAIL PROTECTED]> wrote: > > looks iteresting, you are a clustering expert massimo, what do you > > think about it? Could the exchange mapper be a normal web2py appliance > > in our case? > > > > On Oct 14, 7:36 am, vihang <[EMAIL PROTECTED]> wrote: > > > > > Very interested... but never worked on ruby... > > > > > On Oct 14, 7:41 am, mdipierro <[EMAIL PROTECTED]> wrote: > > > > > > > http://www.rubyinside.com/nanite-self-assembling-cluster-of-ruby-daem... > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
