Well, if I merge your contribution into the wsf library, it will be
included in the release.
Otherwise, we can create a new library  wsf_policy  that would relies on
wsf and extends it to include the WSF_SKELETON_HANDLER and related classes.

Otherwise .. we really need to design tests for WSF since it gets bigger
and more complex.
And we can not afford regression in the future.

Javier, do you think this is where selenium could help?

-- Jocelyn


On Mon, Aug 19, 2013 at 1:03 PM, colin-adams <notifications@github.com>wrote:

> In library/server/wsf/wsf-safe.ecf:
>
> > @@ -18,6 +18,7 @@
> >  		<library name="time" location="$ISE_LIBRARY\library\time\time-safe.ecf"/>
> >  		<library name="uri" location="$ISE_LIBRARY\library\text\uri\uri-safe.ecf"/>
> >  		<library name="uri_template" location="..\..\text\parser\uri_template\uri_template-safe.ecf"/>
> > +		<library name="conneg" location="../../network/protocol/CONNEG/conneg-safe.ecf"/>
>
> Well, you were talking about merging it, but not actually making it part
> of the release.
>
> Anyway, I agree CONNEG needs a review very soon.
>
> Here is a problem I don't know how to deal with:
>
> 1) The server support both JSON and HTML as media-types for a particular
> request.
> 2) The server supports both UTF-8 and ISO-8859-1 charsets (for HTML).
>
> Now suppose the request includes Accept: application/json and
> Accept-Charset: ISO-8859-1 . Accordingly, the negotaiation will be
> accepted. But the JSON spec requires a UNICODE charset (default UTF-8).
>
> Well, i suppose you could say that the user gets what they deserve.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/EiffelWebFramework/EWF/pull/68/files#r5839437>
> .
>