This library is out-of-date

[michaeleisel]

There should at least be a message on the main page stating that this library is out-of-date.

[wuf810]

What do you mean by out of date? No longer required, no longer valid, or doesn't work? You need to be a bit clearer on what you are saying

[michaeleisel]

The library had a number of serious bugs when I used it, and given
that parse's library now covers this functionality and will be maintaining
their code, this library should no longer exist. It only diverts people
from the proper solution of using what parse gives us.

I can see how you might want this library to gain more control over
serialization rather than doing it the parse way. In that case, the readme
should reflect parse's library and the serious bugs should be fixed.

The code base and readme, as is, is a detriment to programmers.

On Wednesday, April 22, 2015, Michael Kaye [email protected] wrote:

What do you mean by out of date? No longer required, no valid, doesn't
work? You need to be a bit clearer on what you are saying

—
Reply to this email directly or view it on GitHub
#27 (comment).

[wuf810]

Thanks for the update. Not sure what the Parse approach is but I find it odd they still haven't added NSCopying to their own code. There are always valid reasons you might need to serialised data (exchanging data with Watch apps for example).

Anyway if this library is buggy and out of date, your point is now clear which is good!

[wuf810]

BTW How do you handle the need for a local version of an PFObject if you don't have network to load it from Parse. That is the main reason we might want to serialise and store i.e. offline mode

[michaeleisel]

Just check out parses pinning and play with it.

On Wednesday, April 29, 2015, Michael Kaye [email protected] wrote:

BTW How do you handle the need for a local version of an PFObject if you
don't have network to load it from Parse. That is the main reason we might
want to serialise and store i.e. offline mode

—
Reply to this email directly or view it on GitHub
#27 (comment).

[drdaz]

Parse gave up on the local datastore (parse-community/Parse-SDK-dotNET#237), and it doesn't perform at all in its current state. This library is still very relevant.