Jump to: navigation, search

This is part of OSC Plug And Play.


The goal of the notification registration is to enable multiple clients to control a given service and still have a consistent view on the service's state even when two clients try to change the same resource at the same time.

Agreed standard


In OSCit, any client that does a request on an object is automatically registered and will get all notifications. A nice side effect of this "all or nothing" architecture is that it enables the construction of very simple and fully asynchronous clients thus producing reactive devices for the end user even when communicating with slow hardware.

When the client hasn't made any calls for a certain time (30 seconds), the server sends a registration time-to-live:


If the client does not respond, another query is made at (45 seconds) and finally the client is removed from observers list.

If a client needs to explicitly register, it can send the register meta method:


The return value of this method is only sent to the caller and contains the current TTL value in seconds.

Personal tools