Hi all,
After labouring over the weekend, I am happy to present the first
version of Gnome's Guide to WEBrick:
http://shogo.homelinux.org/~ysantoso/WebWiki/WEBrick.html
The guide is more of a reference-type documentation rather than
tutorial. I believe that WEBrick is straightforward enough for someone
to grasp its idea. At that point, a tutorial would be of lesser use
than a reference.
Being the first release, I am aware that there are many mistakes:
spelling, grammar (not native English-speaker), obtuse example, etc. I
am also aware that there are missing sections. Some of the missing
sections are listed in the 'NOT YETs' section. If you think there are
other topics I missed, please inform me.
Thank you,
YS.
After labouring over the weekend, I am happy to present the first
version of Gnome's Guide to WEBrick:
http://shogo.homelinux.org/~ysantoso/WebWiki/WEBrick.html
Many thanks to you for this. as a follow up,
is anybody using webrick in production? how does it fare?
i'm thinking of a pure ruby setup if it is feasible. if not,
any recommendations?
stp
eyan
···
--
haaktu technologies
spewing spit since '73
Yohanes Santoso wrote:
Hi all,
Moin!
After labouring over the weekend, I am happy to present the first
version of Gnome's Guide to WEBrick:
http://shogo.homelinux.org/~ysantoso/WebWiki/WEBrick.html
Thank you a lot! I have only taken a quick look at it, (I'm going to read it in depth tomorrow) but it looks like had this nice guide existed earlier I could have spent less time reading source code and more time writing it. Even now, I think that it is still going to be very useful as a reference.
Thank you,
YS.
Kind regards,
Florian Gross
Edwin Eyan Moragas <haaktu@gmail.com> writes:
Many thanks to you for this. as a follow up,
is anybody using webrick in production? how does it fare?
The first WEBrick-based RESTful server I built (see Author's Note) is
in final testing stage now. It will move to production around next
month, if there is no further problem, and so far, there isn't any.
Performance was quite acceptable, and we can scale it easily using
more machines, if needed; but I suspect the database backend is the
limiting factor, not that we have hit a bottleneck yet.
I do not expect a gazillion requests per second to hit the server. But
if there is indeed a gazillion requests per second, I strongly think
I'll have other, more substantial problem, than trying to scale the
server.
i'm thinking of a pure ruby setup if it is feasible. if not,
any recommendations?
Depends on what you are doing. If you are building a hello world
server, then sure. Otherwise, if you need a database backend, then
most likely you need a non-ruby database driver (Ruby DBI is only an
interface to those drivers). Other factors also determine whether a
pure-ruby setup is feasible or desirable.
YS.
Depends on what you are doing. If you are building a hello world
server, then sure. Otherwise, if you need a database backend, then
most likely you need a non-ruby database driver (Ruby DBI is only an
interface to those drivers). Other factors also determine whether a
pure-ruby setup is feasible or desirable.
should have made that more verbose. pure ruby middleware/web server.
i've been looking at iowa and rails (thanks guys). postgres as db.
but as a webserver, been asking myself if webrick is good enough
to be exposed in the open.
right now, i'm playing with cherokee/CGI and ruby. if your
experience with webrick's just fine, i won;t hesitate to use it.
stp
···
--
Edwin Eyan Moragas
Main Expectorant
haaktu technologies
spewing spit since '73
I have not used Iowa + Webrick in production, but I can tell you that in my
testing the performance is surprisingly good. It is actually much better
than I expected out of WEBrick. A PIII 800 Mhz Gentoo Linux box has no
problem pushing 20 connections per second through WEBrick + Iowa with the
webrick example in the distribution.
Kirk Haines
···
On Mon, 23 Aug 2004 13:09:36 +0900, Edwin Eyan Moragas wrote
should have made that more verbose. pure ruby middleware/web server.
i've been looking at iowa and rails (thanks guys). postgres as db.
but as a webserver, been asking myself if webrick is good enough
to be exposed in the open.
right now, i'm playing with cherokee/CGI and ruby. if your
experience with webrick's just fine, i won;t hesitate to use it.
I have not used Iowa + Webrick in production, but I can tell you that in my
testing the performance is surprisingly good. It is actually much better
than I expected out of WEBrick. A PIII 800 Mhz Gentoo Linux box has no
problem pushing 20 connections per second through WEBrick + Iowa with the
webrick example in the distribution.
Kirk, Yohanes,
thanks for the feedback. will let you know what comes out of what
i'm doing.
stp
eyan
···
--
Edwin Eyan Moragas
Main Expectorant
haaktu technologies
spewing spit since '73