Moving the strong context outside the block keeps it alive.
Remove the AFDateFromISO8601String function reference
Update README.md

representationOrArrayOfRepresentationsFromResponseObject had be removed
Fix reverse usage of TTTISO8601DateTransformer

The TTTISO8601DateTransformer has been used in the wrong direction:
instead of converting from a string to a date, it tried to convert from
a date to a string which fails silently everytime.
Update README.md

Updated installation Pod Spec version.
[Issue #201] Adding documentation about caveat of AFIncrementalStoreRequestOperationKey returning single operation in fetch notifications, but an array of operations in save changes notifications.
Merge pull request #203 from t089/master

Fix wrong (reversed) usage of TTTISO8601DateTransformer
Merge pull request #199 from agassiyzh/patch-1

Update README.md
Merge pull request #197 from dulaccc/clean-up

Remove the AFDateFromISO8601String function reference
Merge pull request #206 from ric2z/master

Simply changed the pod spec version on the readme, since all examples are based on 0.4.1
Update README.md
Merge pull request #193 from Spaceman-Labs/features/fix_missing_context

Fixes an always nil context when fetching remote attributes.
Eliminate strong/weak child contexts.

Conflicts:

	AFIncrementalStore/AFIncrementalStore.m
Missed an instance where context saves weren't taking place correctly.

Conflicts:

	AFIncrementalStore/AFIncrementalStore.m
Refactoring managed object context save with exceptional behavior
Locking the persistent store coordinator is not necessary with private queue contexts.
Send fetched objectIDs instead of objects in notification
Use CFAbsoluteTimeGetCurrent() as newValues incremental store node
Fixing deadlock by wrapping AFHTTPRequestOperation success callbacks in context performBlock
Remove unnecessary completion dispatch queue setting for batched requests