9 replies to this topic

[Tarek]

Dear all,

We're really proud to announce that our latest STV 3.0.4 now fully integrates with parse.com! Parse.com is an amazing service that enables you to easily create server-side web services without requiring any coding on your part.

For more details on the integration, please refer to our new book update and the bundled sample application.

Thank you very much for all your support!

[codebonbon]

Nice!

With a brand new documentation pdf. Keep up the good work!

Cheers!

[Paolo Cecchetti]

Thanks

that's great. Parse is my favorite backend since the beta.
Only one concern. One of the most powerful Parse features is the caching system on queries.
But implementing it as Rest service the cache is not available.
So you can rely only on remote data, and full connection.

Any chance to see Parse implemented using the native libraries?

Thanks

Paolo

[Paolo Cecchetti]

It seems there is a way with the latest version of AFNetwork.

The version you delivered with 3.04 doesn't include the

- (void)setCacheResponseBlock:(NSCachedURLResponse * (^)(NSURLConnection *connection, NSCachedURLResponse *cachedResponse))block;

in the AFURLConnectionOperation. I think Matt and Scott added it in one of the latest pulls.

The setCacheResponseBlock should act this way:
Sets a block to be executed to modify the response a connection will cache, if any, as handled by the `NSURLConnectionDelegate` method `connection:willCacheResponse:`.
@param block A block object to be executed to determine what response a connection will cache, if any. The block returns an `NSCachedURLResponse` object, the cached response to store in memory or `nil` to prevent the response from being cached, and takes two arguments: the URL connection object, and the cached response provided for the request.

So I presume that it is something to take account in the STV+WebServices. I hadn't time yet to deeply go into 3.0 code so I only presume it could be possible to implement cache strategies.

Hope Tarek can enlight us:-)

Paolo

[Philip Teagle]

Any example code for using Parse.com persistence of CoreData objects?

[Carlos Torres]

Will there be a posibility to see this example in the near future?

[ahl1]

The missing piece is supporting pointers in Parse. Today STV 3.0 does not support pointers so any relationships cannot be modeled. This means you have to play some tricks with processing the data after a person hits "Done", I believe. Somehow you'd have to set the relationship pointer manually after the fact.

Has anyone tried this?

Tarek your thoughts?

Here is another thread on processing after hitting "Done" but have not tried this - another example would help.
Processing after hitting Done

Also interesting thoughts on Parse Caching - would this mean data is cached as long as the app is running in the background... alleviating local Core Data storage?

thanks!

[Tarek]

Hi guys,

We will be supporting pointers, but we're currently super busy trying to wrap up all the documentation for the end of the month: http://twitter.com/s...345011482804225

[ahl1]

Hi guys,

We will be supporting pointers, but we're currently super busy trying to wrap up all the documentation for the end of the month: http://twitter.com/s...345011482804225

Awesome!
Thank you so much Tarek!

[ahl1]

Do you have a target release date for pointers?
This will help me in design and planning.
Thank you!