Activity level is high. New release again.
Added support for config changes without stopping the running systems,
virt servers can be added, removed and changed without affecting traffic.
As usual, source, docs etc at http://yaws.hyber.org
From: Bruce Fitzsimons <Bruce@Fitzsimons.org> - 2004-12-16 02:32:32
Claes Wikstrom wrote:
>Activity level is high. New release again.
>Added support for config changes without stopping the running systems,
>virt servers can be added, removed and changed without affecting traffic.
Nice work, that counters one of the objections I have to the "one
instance of yaws but many webapps" email still sitting in my drafts
folder. I'll reply eventually...its the single mnesia instance thing
thats annoying me.
Is the DNS resolving cached? non-blocking? Should I just go and read the
> Is the DNS resolving cached? non-blocking?
It's the regular erlang resolver that is used i.e. inet:gethostbyaddr/1 which
is a caching resolver. As for non-blocking, the erlang resolver is non-blocking
in the sence that it just blocks the erlang process that calls the
resolver. There is no async
interface to the reolver routines in erlang. It's typically never
needed since processes
are light. At least in the case of Yaws, the block-this-process semantics of
inet:gethostbyaddr/1 is just fine.
Yaws has one process per HTTP socket, blocking just that process while
resolving is ok.
The default value for this (resolving peers at runtime) is off and
should probably only be
used by low-volume sites. If traffic load is high, it's certainly much better to
post-process the logfiles. I have no idea of how much this affects
performance, probably some.