On 24 Sep 2008, at 17:19, [EMAIL PROTECTED] wrote:
On Wed, Sep 24, 2008 at 04:53:35AM -0400, Ian Boston wrote:
Looks ok, but needs some javadoc and may need some SPI methods
outside
the Spec to make it meaningful. Depends on if we think Shindig
scope is
purely to the spec, or if it should go just far enough to be a
running
RI of OpenSocial.
Working on the javadoc and the handler's test.
great :)
About the scope, I would say having a reference implementation (I
assume
that's what you mean by RI) is way more useful.
yes RI == Reference Implementation
I will implement some
reading methods in the sample classes anyways, but I don't feel
qualified yet to propose a SPI API.
Ok, I think the query mechanism in the other Services is a workable
pattern and if binds well to the REST interface.... but.... I am
almost certain that reading messages to present back to the user is a
container thing, and might be outside scope for use by a gadget
directly, and hence not part of OpenSocial...... however, I can see
use cases that say gadgets need access to their own message feeds...
probably needs to be discussed on the spec list.
Another question. No matter how hard I look, I cannot find in the
spec a
description on how the post message method is suposed to get the
list of
recipients. It's not part of the proposed URI template (and I can't
see
how to fit it there) and it's not part of the post body either, as
that's supossed to be just the message itself. Am I missing something
obvious here?
I also couldnt see anything, it might be something that is missing
from the Spec, that only becomes apparent on implementation.
Anyone ?
Ian
