Hi! We found an unexpected behavior when we perform multiple *restaurant-by-date* requests at the same time using different timestamps. Some of the responses that we get do not correspond with the solicited timestamp [unexpected_time_stamp.png]. If we add a little timeout before send each new request, the issue does not happen. We think that it could be a minor performance issue but it is not too important because it's a starter guide and we can control it from the client. Furthermore, we think that it will be kept in mind for scalability purposes. Regards, ULPGC team. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-developer-experience/attachments/20160217/f0044ceb/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: unexpected_time_stamp.png Type: image/png Size: 604479 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-developer-experience/attachments/20160217/f0044ceb/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy