a question about the project's aims

[Jeffrey 'jf' Lim]

hi, sorry if this has been asked before - but I searched, and found nothing...

From the front page of ebb at rubyforge - "It is not meant to be a full featured web server" - i'm just wondering, any specific reason why not? I would imagine (and i believe some others would agree with me as well) that Ebb would make for a great front-end public facing web server (instead of an nginx, + a cluster of app servers behind) - it appears to be the perfect combination of what i would look for in a rack app deployment. Web front end, 1-layer translation to rack and that's it. As opposed to a web front end (nginx), then another web layer (nginx, to whatever app server), then to rack.

What would be needed (apart from what has been pointed out already - multipart parsing, and http expect) in order to get Ebb to be "a full featured web server"?

-jf

--
In the meantime, here is your PSA:
"It's so hard to write a graphics driver that open-sourcing it would not help."
-- Andrew Fear, Software Product Manager, NVIDIA Corporation
http://kerneltrap.org/node/7228

[ry dahl]

The idea is to embed http servers in different environments. in the
Ruby interpreter, for example. Typically these environments that it is
embedded into are quite slow and do much better behind a load balancer
in multiplicity.

Besides the fact that you would want a fast load balancer in front of
any large website, Ebb lacks support for SSL and static file serving.
The later I would like to add in the next versions, but I have no
intentions of supporting SSL.

Supposing SSL support was added and a few other things, the ebb c
library could be used to write a small load balancer (hmm - which
isn't such a bad idea!) But I would not want the Ruby interpreter up
front and center, naked against the harsh winds of the web.

ry

[Jeffrey 'jf' Lim]

On Thu, Jun 19, 2008 at 12:11 AM, ry dahl <ry....@googlemail.com> wrote:

The idea is to embed http servers in different environments. in the
Ruby interpreter, for example. Typically these environments that it is
embedded into are quite slow and do much better behind a load balancer
in multiplicity.

hm, gotcha. But would adding whatever's necessary (ok, leaving the ssl aside) to be "full-fledged" really be so large in size that it could not fit in an embedded environment?
 

Besides the fact that you would want a fast load balancer in front of
any large website, Ebb lacks support for SSL and static file serving.
The later I would like to add in the next versions, but I have no
intentions of supporting SSL.

right. SSL is another thing altogether.
 

Supposing SSL support was added and a few other things, the ebb c
library could be used to write a small load balancer  (hmm - which
isn't such a bad idea!) But I would not want the Ruby interpreter up
front and center, naked against the harsh winds of the web.

hey, the state machine protects it, right? ;)

-jf