Re: [ANN] Resin-3.0.0 beta release!

On the same subject, is there a particular reason to use
select ?
I recall that select has a maximum file descriptor limit (1024) and that
it gets slower as number of file descriptors grow.

As far as the limit is concerned it's my understanding that poll is
better than select.

Apart from that, on linux there is a new feature dubbed 'epoll' which
seems to be faster than any of the other methods.

I guess what I'm trying to ask is:

- am I talking nonsense, ie. you could probably circumvent the select
limits by selecting only sub groups of your fds or any crazy tekneek

- would it be possible to pluginize the code a little bit so that you
could write new plugins easily, like an epoll plugin, a bsd kqueue
plugin, etc...

Thanks anyway and bravo for the new release !
Stefan

On Fri, 2003-02-14 at 11:42, Boris Granveaud wrote:
> Hi,
>
> I'm a little puzzled by the chapter on Non blocking I/O in the release
> notes:
>
> - I thought that you were going to use JDK 1.4 NIO, instead it seems
> that you have chosen a JNI implementation. Could you explain us?
> - I understand that NIO is used only for keepalive connections, isn't it
> used during the request/response processing?
> - will there be a Windows implementation?
>
> Thank you,
>
> > Release notes at
> > http://www.caucho.com/resin-3.0/features/resin-3.0.0.xtp.
> >
> > A few notes:
> >
> > 1) Resin 3.0.0 is a major rewrite. That's one of the reasons we're
> > calling it beta. The other reason is that we might tweak the
> > configuration before we have a final release.
> >
> > 2) The standalone server has been stable in our testing. So some
> > sites may be able to use Resin 3.0.0 for deployment. Stress testing
> > would be a very good idea.
> >
> > 3) The plugins, Apache and IIS, are much less stable. In particular,
> > the load-balancing features have not yet been added to the plugins. A
> > single Resin server with Apache/IIS should be fine. The plugins, by
> > the way, no longer read the resin.conf. They query the backend server.
> >
> > 4) There have been a number of configuration changes. Most of them
> > are documented in the release notes. Because we do expect to make
> > Resin 3.0 backwards compatible with Resin 2.1, please report any
> > discrepancies on the bug tracker. (Resin 3.0.0 already has some known
> > issues with backwards compatibility, but report the bugs anyway.)
> >
> > 5) Please report any bugs in the bug tracker. You can also post them
> > in resin-interest, but there's a chance that they'll disappear if you
> > don't report them in the tracker.
> >
> > 6) We're making good progress on the documentation, but there's still
> > a good amount of docs that haven't yet been updated to Resin 2.1.
> >
> > share and enjoy!
> >
> > -- Scott
> >
> >
> >

-- 
Stefan Praszalowicz <stefan@xxx.com>
Avedya