From: Roman R. <rro...@ac...> - 2004-06-08 16:54:02
|
> Yours is a good case (for which it will be interesting to hear > replies) but it does not match mine 100%. I have not a) as a > requirement (although it would be a nice thing to have), and instead I > have > > c) the same server process that serves database connections needs to > provide other services to remote clients, using different ports and > protocols, including but not limited to SOAP and HTTP. For those who > are concerned about the scalability of my all-in-one solution, don't > worry: The workload is never going to be heavy. It was not intended to be your case :) Since Sean is not buying c), I created a case, pretty legal one, when Jim's solution is the only possible one. Maybe he buys this one :) Anyway, I do not think that anybody will do a release of such "embedded superserver", and after Vulcan merge it will no longer be an issue. I'm afraid you have no other choice then to build it yourself or to find some other incentives to involve Dmitry for example in your project. Roman |