Hi, In large-scale utilization scenarios (e.g. 100,000 entities registered) a NGSI10 queryContext with too wide patterns (e.g. the ".*" that matches everything) could be overwhelming (e.g. it could involve an XML payload containing 100,000 entities information in the HTTP response to the client). A similar case could happen with NGSI9 discoverContextAvailability operation. We should provide a solution for these cases: * In the short term (i.e. for Release 2), we could just define a new error code (e.g. "483 Response Too Long") that the NGSI server could use if a given limit is exceeded (and particular limit will be implementation specific). * In the long term, probably we should define a smarter mechanism. Looking to other populars REST APIs one trend is to use paging, e.g. the Twitter API (https://dev.twitter.com/docs/api/1/get/search) uses "rpp" and "page" to specify how many items to include in the response, maybe a similar mechanism could be introduced in NGSI. What do you think? Best regards, ------ Fermín ________________________________ 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/20130227/b3b4f1ea/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy