Re: Input on request for link relation

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/11/09 10:52 AM, Kris Zyp wrote:
> 
> Sam Johnston wrote:
> 
>> Well spotted. For me to "monitor" or "watch" something requires
>> conscious, ongoing effort by the client. The dictionary definition
>> <http://www.google.fr/search?q=define:monitor> supports this:
>> '/keep tabs on; keep an eye on; keep under surveillance; "we are
>> monitoring the air quality"; "the police monitor the suspect's
>> moves"/'. It's a nitpick but I wonder if there are use cases for a
>> "monitoring" interface (e.g. for polling) - for example a site
>> offering a link that an uptime monitoring service could use to to
>> test the various subsystems, or an actual monitoring service?
> 
>> OTOH terms like "notify" and "push" imply a passive rather than
>> active role for the client ("update" is out because it can be
>> confused with "edit" - in that the resource itself is being
>> updated).
> But SIP is not a polling protocol is it? Is there something about SIP
> that is more "monitor-ish" than pubsubhubbub that necessitates a new
> relation name? And if so, how do I determine which relation name
> should be used for servers that connect to Dojo clients to send
> notifications?

The 'rel' says only "this is the kind of place where you can receive
notifications about changes to the resource". That doesn't say *how* you
receive those notifications. If the URI is sip:foo then perhaps you need
to poll. If it's xmpp:bar then perhaps you receive pushes. But the "how"
doesn't change the fact that this is where you can get notifications.

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqqh5wACgkQNL8k5A2w/vwo/wCgpeN4bAidIv9zMU0O6Zo/q6P9
O+sAoItSWp5s+xtWkNDNAiD+tJl6nvys
=Pm91
-----END PGP SIGNATURE-----

Received on Friday, 11 September 2009 17:24:23 UTC