Re: [cf-dev] Recommendation for updating a resource thresholds in Califo

["Kovatsch Matthias" <kovatsch@xxxxxxxxxxx>]

It is not fully clear to me how you assign the roles (which component is client and which server) and who has the initiative (sends requests to where). As Kai mentioned, OMA Lightweight M2M might give you a good guidance on how to design the overall application on top of CoAP:

http://www.slideshare.net/MichaelKoster/ietf91-ad-hoccoaplwm2mipso-41542196
http://openmobilealliance.hs-sites.com/lightweight-m2m-specification-from-oma

Ciao
Matthias

> -----Original Message-----
> From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Jamal Mouline
> Sent: Sonntag, 16. November 2014 08:30
> To: cf-dev@xxxxxxxxxxx
> Subject: Re: [cf-dev] Recommendation for updating a resource thresholds in
> Californium?
> 
> Thank you for the recent update
> General question about the proper coap method(s) for updating a resource
> thresholds
> 
> For example, the device is monitoring a sensor temperature and, as a client,
> we want to trigger an alarm event to the server if such temperature goes
> above (below) a maximum (minimum) threshold value
> 
> From a protocol standpoint, we understand the best method to query the
> temperature value is by using a URI-QUERY on the temperature resource,
> how about the proper method for the server to set up thresholds on the
> device? Where would the threshold values be communicated to the client?
> ETAG option? Payload? Others?
> 
> Similar questions when the resource is the device location (25 bytes for
> lag/long in decimal format) and the threshold this time is a geofence box (100
> bytes for 4 lat/long points)
> 
> Thank you and kind regards,
> Jamal Mouline
> Connected Development
> 
> -----Original Message-----
> From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] On
> Behalf Of cf-dev-request@xxxxxxxxxxx
> Sent: Sunday, November 16, 2014 12:00 PM
> To: cf-dev@xxxxxxxxxxx
> Subject: cf-dev Digest, Vol 4, Issue 9
> 
> Send cf-dev mailing list submissions to
> 	cf-dev@xxxxxxxxxxx
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://dev.eclipse.org/mailman/listinfo/cf-dev
> or, via email, send a message with subject or body 'help' to
> 	cf-dev-request@xxxxxxxxxxx
> 
> You can reach the person managing the list at
> 	cf-dev-owner@xxxxxxxxxxx
> 
> When replying, please edit your Subject line so it is more specific than "Re:
> Contents of cf-dev digest..."
> 
> 
> Today's Topics:
> 
>    1. Another update that might break your code (Kovatsch  Matthias)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sat, 15 Nov 2014 23:31:47 +0000
> From: "Kovatsch  Matthias" <kovatsch@xxxxxxxxxxx>
> To: "Californium (Cf) developer discussions" <cf-dev@xxxxxxxxxxx>
> Subject: [cf-dev] Another update that might break your code
> Message-ID:
> 	<55877B3AFB359744BA0F2140E36F52B52B8F5221@xxxxxxxxxxxxxxxx
> >
> Content-Type: text/plain; charset="us-ascii"
> 
> Dear list
> 
> There will be another push that might break your code: I refactored the
> NetworkConfig so that the key constants are in its proper place and I
> removed broken entries and renamed others to be consistent with the
> terms in the documentation. Still a lot to do to become stable for 1.0 :P
> 
> Ciao
> Matthias
> 
> 
> ------------------------------
> 
> _______________________________________________
> cf-dev mailing list
> cf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit https://dev.eclipse.org/mailman/listinfo/cf-dev
> 
> End of cf-dev Digest, Vol 4, Issue 9
> ************************************
> _______________________________________________
> cf-dev mailing list
> cf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit https://dev.eclipse.org/mailman/listinfo/cf-dev