[Fiware-ngsi] UpdateContextAvailabilitySubscriptionRequest

[Fermín Galán Márquez]

Dear Tarek,

I agree with Tobia's interpretation.

Best regards,

------
Fermín

El 06/12/2013 9:44, Tobias Jacobs escribió:
Hi Tarek,

Yes, I guess the idea was somehow that the reference (i.e. the place where the notifications go to) will not be changed when updating the subscription.

By the way, NGSI 10 is even more radical, as in the updateContextSubscriptionRequest you cannot even change the set of entities and attributes subscribed to.

Best
Tobias

From: fiware-ngsi-bounces at lists.fi-ware.eu<mailto:fiware-ngsi-bounces at lists.fi-ware.eu> [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of t.elsaleh at surrey.ac.uk<mailto:t.elsaleh at surrey.ac.uk>
Sent: Donnerstag, 5. Dezember 2013 21:30
To: fermin at tid.es<mailto:fermin at tid.es>
Cc: fiware-ngsi at lists.fi-ware.eu<mailto:fiware-ngsi at lists.fi-ware.eu>
Subject: [Fiware-ngsi] UpdateContextAvailabilitySubscriptionRequest

Hello Fermin,

I want to ask about this. The "SubscribeContextAvailabilityRequest" holds a "reference" parameter, but "UpdateContextAvailabilitySubscriptionRequest" does not.

Is this intentional?

Best regards,
Tarek



________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20131209/3cd7be07/attachment.html>