- From: Sandeep Shetty <sandeep.shetty@gmail.com>
- Date: Wed, 17 Oct 2012 00:19:36 +0530
- To: Antonio Tapiador del Dujo <atapiador@dit.upm.es>
- Cc: public-fedsocweb@w3.org
> After carefully reading the ActivityPump API, I like the approach. I think > that federating directly with AS is more straightforward than the > PuSH/Salmon mix. I'm guessing you mean federating using the ActivityPump API, which is what is equivalent to PuSH+Salmon mix (which can also use AS as a format). > We are close to comply with SWAT0 using OStatus in Social > Stream, and the feeling is that PuSH and Salmon are somewhat repeated, > besides XML is too verbose. Except for the payload (activities), what other things do you feel are repeated? > The last can be described using JSON AS + Audience Targeting + Responses. I > think that federation between sites could be achieved with only one activity > point per site. This way, notifications to several users in the same site > could be delivered only once. I prefer the other model with an endpoint per user, because if done right (playing nicely with the web and HTTP), you get all the advantages: like for example, issuing a 301 response to notify a user has moved. -- Sandeep Shetty
Received on Tuesday, 16 October 2012 18:50:27 UTC