FreeLists / openbeosnetteam / [openbeosnetteam] Re: one replicant for everything?

[Waldemar Kornewald <wkornew@xxxxxxx>]

jonathanthompson@xxxxxxxxxxxxxxxxxxxxxxx wrote:
> I guess I'm paranoid, but I'm thinking that using something like the Media Server's parameter web might be a better solution: don't have all the various things running in the same process, but rather have them send data representing their state to the same process, so if one goes pear-shaped, it doesn't affect all the others.  I may be misunderstanding what you're saying, though: do you mean create an Uber Replicant that can be copied from one machine to another, sort of like an executable version of what Windows does with roaming profiles?  If so, using a replicant in that manner scares me that much more: it only requires one unexpected bit of missing or wrong data for something in that replicant to fail and seg fault, if the replicant isn't written correctly to handle that, and then you're likely to have a Mutantcant (mutant replicant where it didn't replicate successfully) that's sort of like a virus, in that each time you move it to another machine, it messes up that m
ach
>  ine, too.  Did I interpret things wrong?
>
> Jonathan Thompson

Sorry, but I don't really understand what you want to say. I'm only 
suggesting to move basic networking functionality into one single 
replicant instead of cluttering Deskbar with many of them. If one of 
them crashes Deskbar will crash, too. So, it makes no difference if you 
have one or many replicants. They must be rock-solid, anyway.
Maybe did not explain well enough...someone else having complaints?

Bye,
Waldemar