Hi,
According to the wikipedia page (http://en.wikipedia.org/wiki/JSON-RPC)
notifications are indeed a part of the specification.
This is also backed by the actual specification, although more reading is
required (http://www.jsonrpc.org/specification#notification):
>From Section 2:
"All member names exchanged between the Client and the Server that are
considered for matching of any kind should be considered to be
case-sensitive. The terms function, method, and procedure can be assumed to
be interchangeable.
The Client is defined as the origin of Request objects and the handler of
Response objects.
The Server is defined as the origin of Response objects and the handler of
Request objects.
One implementation of this specification could easily fill both of those
roles, even at the same time, to other different clients or the same
client. This specification does not address that layer of complexity."
And finnaly from section 4.1:
"A Notification is a Request object without an "id" member. A Request
object that is a Notification signifies the Client's lack of interest in
the corresponding Response object, and as such no Response object needs to
be returned to the client. The Server MUST NOT reply to a Notification,
including those that are within a batch request.
Notifications are not confirmable by definition, since they do not have a
Response object to be returned. As such, the Client would not be aware of
any errors (like e.g. "Invalid params.","Internal error.")."
I have implemented this with jsonrpc-cpp, but I don't remember exactly what
I changed (if anything).
If you're interested I could try to make a nice patch for it?
// Fredrik
On Sat, Dec 22, 2012 at 9:21 AM, Sebastien Vincent <
seb...@cp...> wrote:
> Hi Andrey,
>
> Do this feature is part of the official JSON-RPC specification ?
>
> Anyway this feature seems interresting to me but currently I am a bit
> busy. I will be more than happy to review patches.
>
> Regards,
> --
> Seb
>
> Le 19/12/2012 21:17, Andrey Gursky a écrit :
> > Dear Sebastien,
> >
> > the so called "server-side" notifications are described here:
> > http://wiki.xbmc.org/index.php?title=JSON-RPC_API#Notifications.
> >
> > What do you think about such feature? Or is there any good another
> > design pattern that could avoid polling from clients.
> >
> > Regards,
> > Andrey
> >
> >
> ------------------------------------------------------------------------------
> > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> > Remotely access PCs and mobile devices and provide instant support
> > Improve your efficiency, and focus on delivering more value-add services
> > Discover what IT Professionals Know. Rescue delivers
> > http://p.sf.net/sfu/logmein_12329d2d
> > _______________________________________________
> > Jsonrpc-cpp-devel mailing list
> > Jso...@li...
> > https://lists.sourceforge.net/lists/listinfo/jsonrpc-cpp-devel
> >
>
>
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Jsonrpc-cpp-devel mailing list
> Jso...@li...
> https://lists.sourceforge.net/lists/listinfo/jsonrpc-cpp-devel
>
|
