Well, if the SE/ME groups end up shipping a client API then I can see more
server implementations focusing only on the server end of things but you're
probably right about that at least in the short term.
On Mon, Feb 4, 2013 at 11:49 AM, Mark Thomas <mark_at_homeinbox.net> wrote:
> On 04/02/2013 10:32, Justin Lee wrote:
> > I'm talking to Henrik Stahl here at Jfokus and he was asking about
> whether
> > the spec allows implementors to provide only the client or the server API
> > and still be compliant. He's looking for feasibility of including
> clients
> > into the SE and ME products. As I read it now, the spec implicitly
> > requires both client and server in order to be a compliant
> implementation.
> > Is it possible at this point to include language that allows for
> either/or
> > for those implementors who don't care about one end or the other?
>
> The client API is very almost a subset of the server API. I can see a
> case for the allowing client only or client and server but I am not
> convinced about server only.
>
> Mark
>
>
--
You can find me on the net at:
http://antwerkz.com http://antwerkz.com/+
http://antwerkz.com/twitter http://antwerkz.com/github