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.
Hi there,
Just wondering if there has been any update on the WebSockets request. We would like to integrate a messaging component, and this would be a great feature.
Thanks!
Hello Will,
It looks like this request originated before my time at Kinvey. Let me look into this and I will get back to you as soon as possible.
Regards,
Billy Gee
Kinvey Support
Hello Will,
We do not support WebSockets today. However, we do have an offering called Kinvey Live Service that might suit your needs. It is not GA yet but it should be available soon. We will let you know as soon as it is GA and deployed.
Please let us know if you have any questions.
Regards,
Billy Gee
Thank for the reply Billy!
Is there any anticipated launch date in place. We would be more than happy to do some testing if that is an opportunity.
Thanks!
Hello Will,
There will likely be an Early Adopter release as well as a formal GA release. We probably will not have target dates for those events until later this month. I will be happy to let our VP of Product that you are willing participate in an early release of the product. We will confirm with you when the dates are available and if and how you would be able to participate prior to GA.
Regards,
Billy Gee
Jason Barron
var animalSocket = new WebSocket("wss://baas.kinvey.com/appdata/kid_MyApp1D/animals", ["apiVersion3"]);
animalSocket.onopen = function (event) {
animalSocket.send(JSON.stringify({authToken: "abcd123456789"}));
};
...
animalSocket.onmessage = function (event) {
console.log("Got a new animal");
console.log(JSON.parse(event.data));
}
Then when someone else adds an animal to the collection (assuming I have access to it via the ACL), I would receive a message ideally containing the new object, but alternatively just a notification that "hints" that I should GET a given collection or entity again since it has been updated.
An alternative to having a socket on each collection with a more generic solution might be just to have one per application ID and make the messages more generic like:
{
action: ["created" | "retrieved" | "updated" | "deleted"]
collection: "animals"
}