As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
Since Kinvey has pretty good support for offline access, I think it would make sense if the database layer cached an ETag for each model and collection (could be stored in the object's body) so that when the data was fetched from Kinvey with a 'If-None-Match' header including the ETag, the server would return a 304 Not Modified response if the content was the same and the client libraries could pass the cached version up to the client application. This would reduce mobile data traffic quite a bit.
1 Comment
I
Ivan Stoyanov
said
over 9 years ago
Most certainly. This has been on our roadmap for a while.
Jason Barron