Replying to Avatar Vitor Pamplona

Here's a question for you. I was considering a replaceable event that is updated by the provider all the time as opposed to a request/response procedure protocol.

A replaceable event will be easier to code by clients (just subscribe to event x) but I didn't know if it made sense for providers to keep updating a list of recommendations every time a new post comes into the list.

Now that you have coded it, do you think the request/response procedure was a good choice?

Avatar
brugeman 2y ago

One huge downside here is privacy - everyone can see what requests I am making. We could encrypt the content and filters, but that's still annoying

Reply to this note

Please Login to reply.

Discussion

No replies yet.