"but it's quite funny, very often the reply events are showing up ahead of the replied to events in the feed"

LOL how the heck?

Reply to this note

Please Login to reply.

Discussion

subscriptions often come ahead of req results... usually a req starts a subscription first, and then does the search and then sends the results

in the meantime, the subscription is there and if someone publishes a matching event it sends that out, and the database could still be working at that point

makes sense, when you think about it... subscription results can come in without a search, but reqs always need a search

basically subscriptions match on newly submitted events before they go to the database, so if the req is busy but the sub is open already a reply can come first because the req thread is busy saving it first

er, searching it lol

Okay, that makes sense. Unexpected.