From: Dannes W. <da...@ex...> - 2012-11-13 10:11:21
|
Hi, On Tue, Nov 13, 2012 at 12:12 AM, W.S. Hager <ws...@gm...> wrote: > Well, that would all be fine if there weren't already issues with db > corruption and memory overconsumption. My concern is you guys make exist as > lean & mean as possible this time, and focus less on support. Well actually nothing has changed in eXist-db for 'the war feature', only a configuration file has been changed. Nothing more.... (We try to provide as much as support as possible on this list, but well, it is a job done by volunteers, doing this in spare time..) > It has to run out of the box, and that's that. We all agree on this > but I have a hunch that the whole servlet container deal is a design > flaw. The more processes/instances the merrier. > Well, actually the jetty servlet container is the fundament of eXist-db; We selected jetty because it is open source, well supported and it is rather a light engine. We decided a long time ago not to develop our own HTTP server but to use off-the-shell technology as much as possible. This way we can focus better on the core-business..... developing the database. I am sorry to read you are a bit disappointed in eXist-db as a product (the upcoming 2.0, current development wor,k might give you a better experience..... when it is ready). Maybe we should talk offline a bit further on your specific issues.... cheers Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |