Hi,
Am 08.02.2013 um 23:55 schrieb Matt Miller linuxw...@outer-planes.net:
In working on the patch to address HTTP pipelining, I cascaded into section
16: Multiple Streams.
Multiple Streams seems to require support for HTTP pipelining, but feels as
if it runs afoul of even the basic
Pubsub is different but PEP shares it's subscriptions with roster, so
you may look at your roster as on your Friend list and build a
protocol to share your friend list. What's wrong with it?
On 02/11/2013 11:02 PM, Ashley Ward wrote:
The problem with this list being maintained by the server is
On 02/12/2013 01:29 AM, Jaussoin Timothée wrote:
The user's server could track all their subscriptions, but this would be
prone to errors and would necessitate their server understanding pubsub to
some extent.
What errors? Unfortunately, with PEP server must understand pubsub
anyway so I don't
I understand that you want to do lookup in PEP. I'd be very wary of
depending on it to build a full scaled social platform.
We tried using PEP to build buddycloud. We created a bunch of nodes for
each and would push out updates based on presence. This kinda worked with
the following caveats::
-
On Tuesday, February 12, 2013 08:34:42 AM Simon Tennant wrote:
One solution that might give you some milage: using DISCO to point to a pub
sub component that is nominated for social activities? (Something like https
://buddycloud.org/wiki/XMPP_XEP#buddycloud_Server_Discovery). This will
give
