dev-serveez
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [dev-serveez] upcoming release


From: Raimi 'Raimi' Jacob
Subject: Re: [dev-serveez] upcoming release
Date: Tue, 5 Feb 2002 15:02:39 +0100 (CET)

On Tue, 5 Feb 2002, stefan wrote:

hi!

>   I'd like to make a new release of Serveez.  Do you think it's worth?
yeah, it's time.

> Any more items to consider, todo?
nope.

>   And how do you like this announcement text?
> ======================================================================
> GNU Serveez 0.1.3 has been released. 
> 
> GNU Serveez is a server framework; it provides routines and help for
> IP-based servers (TCP, UDP and ICMP) as well as "named pipes" for all
> connection-based protocols.

this looks strange (esp. the last part) perhaps:

GNU Serveez is a server framework; it provides routines and help for
IP-based servers (TCP, UDP and ICMP) as well as "named pipes". It
demonstrates portable network programming with good performance.

... or something like that. the adjective "performant" is missing in
english :-)

> It is available from ftp://ftp.gnu.org/gnu/serveez/ and mirrors of that 
> site (see list of mirror sites at http://www.gnu.org/order/ftp.html).
> 
> Changes in this release:
> 
>   The current release of Serveez has improved its built-time 
> behaviour a lot.  It provides support for cross-compiling and 
> workarounds for SunOS/Solaris and MacOS quirks.

  The built-time behaviour has been greatly improved. Serveez now supports
cross-compilation and provides workarounds for SunOS/Solaris and MacOS X
quirks.

>   In the new version the user will find basic coserver functionality,
> Guile version 1.3 backward compatibility code and RPC service support
> in the Guile frontend.

okay...

>   The builtin HTTP server now also provides partial contents.  The
> core library itself is able to handle INADDR_ANY bindings (indicated by 
> the keyword `any' in network port configurations) and appropiate mixtures 
> of this binding with explicit network interface bindings.  Also it 
> allows SO_BINDTODEVICE bindings by the `device' property of the port 
> configuration.

this part looks strange too, but is okay, i guess. perhaps it's not
necessary to name the `any' and `device' things. perhaps just mention that
it is possible. also "appropriate mixture" looks strange. perhaps:

  The builtin HTTP server now supports partial contents. The core
library is able to do INADDR_ANY as well as SO_BINDTODEVICE bindings.
It also supports mixing any possible bind option.

> ======================================================================

mmh. not quite good yet...

Bye,
    Raimi

--
      __/\     _/\    _____/\.___/\
     /   /    /  /___/   ____/  __/\     Name    : Raimi
    /   /  __/    __/   / __/  / _\/     Contact : address@hidden
   /   /__/ /     \/   /_/_/  /_/        Visit   : http://www.lkcc.org
  /________/___/\._\._____/_____/\       3.141592653589793238462643383
  \._______\.__\/__/\.____\.____\/       27950288419716939937510582097





reply via email to

[Prev in Thread] Current Thread [Next in Thread]