Well, it will be no new features as such.
Main thing will be the API refactoring, to make SHTTPD the best embeddable
choice.
I already discussed it briefly with people from transmission project (
transmissionbt.com),
who use SHTTPD already.
On Wed, Sep 24, 2008 at 1:20 PM, Laurie Gellatly
<[EMAIL PROTECTED]>wrote:
> Hi Sergey,
>
> What feature list are you working to, hoping to support?
>
> I still use version 1.35 as it has the defined table of URI as in the
> embedded application that makes sense.
>
>
>
> …Laurie:{)
>
>
>
>
>
> *From:* Sergey Lyubka [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, 24 September 2008 10:04 PM
> *To:* shttpd-general
> *Subject:* [shttpd-general] Announcement: next version will be SHTTPD 2.0
>
>
>
> Hi shttpd users!
>
> Next version of SHTTPD will be 2.0, with several major changes:
> The focus is moving towards the ease of embedding.
>
> 1. Source code will be back in one file, shttpd.c
> 2. Each connection will be handled by separate thread. This will simplify
> callback code greatly, allowing for blocking calls.
> 3. Thus, an API will change. Draft API is at
> http://silversoft.net/~devnull/tmp/shttpd.h<http://silversoft.net/%7Edevnull/tmp/shttpd.h>
>
> Standalone versions are not expected to be any different in functionality,
> although I plan to remove some command line flags that I think are not
> needed:
> -mime_types,
> -cgi_env
>
> Comments are more than welcome.
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
shttpd-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shttpd-general
