We were talking with Ono today about merging all jabberd 2 sub applications (router, c2s, s2s, sm) into one binary, with multiple threads running each components. That would mainly reduce maintenance and deployment effort. You would run one process instead of several ones. And wouldn't keep one from running each component in separate process - just run only one thread+component in each instance.
With such design there are some performance optimisations possible in router, that could just pass pointers to data instead of pushing the data through TCP sockets. There are some problems with current single-thread design of jabberd, but we think they are easily solvable. Ex. static buffers with thread local-storage. What do you think about this idea? Is it worth pursuing? Or not worth the effort? -- /\_./o__ Tomasz Sterna (/^/(_^^' http://www.xiaoka.com/ ._.(_.)_ im:[EMAIL PROTECTED] -- To unsubscribe send a mail to [EMAIL PROTECTED]
