Open crsantos opened 8 years ago
@crsantos literally working on this right now. It will prevent the need to use the custom notification handling with RBQRealmNotificationManager
Sorry, mis-clicked and forgot to paste the rest of the question :D WoW! Many thanks! If you need something just shout
@crsantos well scratch my first idea, I don't think I can drop RBQRealmNotificationManager
yet unless a performance hit is acceptable. Diffing the collection is pretty costly once there are more than a couple hundred items.
As a result, using the collection notification in exchange for the current Realm notification in RBQRealmNotificationManager
doesn't actually improve anything.
Realm is getting close to launching true fine grained notifications that include specific object changes, which then can be incorporated into RBQFRC. Once that is released RBQFRC will be irrelevant unless you want its sectioning ability. Realm doesn't yet support groups, so the index changes off its upcoming fine grained notifications will only be based on 1 section, but RBQFRC can fill in the gaps there. Until then, I think I am just going to leave things as is.
Thought about that performance tradeoff too. Maybe it's better to leave it as it is: using the mark as dirty approach. Let's hope Realm launches that quickly :)
Any update on this?
This is more likely a doubt than an issue. So please tag it accordingly.
I don't know if this makes sense but, is there any improve if we use the new Collection Notifications from Realm's 0.98? I'm just asking you that you have the know-how about this codebase so is it worth trying to use those notifications?
Thanks