CloudKit Now Supports Server-To-Server Web Service Requests
developer.apple.com
CloudKit Now Supports Server-To-Server Web Service Requests
1–10 of 18 posts
Re: CloudKit Now Supports Server-To-Server Web Service Requests
#2About 3-4 years too late. This should have been released with iOS5/iCloud - when it might have been useful.
Re: CloudKit Now Supports Server-To-Server Web Service Requests
#3About 3-4 years too late. This should have been released with iOS5/iCloud - when it might have been useful.
Yeah - nobody was using parse, which proves there is no demand for this kind of thing.
/s
Re: CloudKit Now Supports Server-To-Server Web Service Requests
#4This is a good step. I expect to see a whole slew of cloudkit dashboard services pop up soon.
Re: CloudKit Now Supports Server-To-Server Web Service Requests
#5Re: CloudKit Now Supports Server-To-Server Web Service Requests
#6Re: CloudKit Now Supports Server-To-Server Web Service Requests
#7Re: CloudKit Now Supports Server-To-Server Web Service Requests
#8About 3-4 years too late. This should have been released with iOS5/iCloud - when it might have been useful.
CloudKit JS has only been released 6 months ago and that was my biggest request concerning it, I'm happy they didn't wait until WWDC 2016 to add this support.
Re: CloudKit Now Supports Server-To-Server Web Service Requests
#9Anyone know the latencies associated with an URL request?
Are we talking 15ms range? 150ms range? 600ms-1s range?
Also, can we access binary blobs/files/images via this API? It seems the max file size of an asset field is 15mb, which is smaller than a Raw photo.
Re: CloudKit Now Supports Server-To-Server Web Service Requests
#10About 3-4 years too late. This should have been released with iOS5/iCloud - when it might have been useful.
Yeah - nobody was using parse, which proves there is no demand for this kind of thing. /s
What makes you say no one was using it (my understanding is the opposite), and that most certainly does not lead to your conclusion even if the first part is true.
Just because FB killed it doesn't mean it no one was using it...