Since OSW is based on XMPP and OStatus is based on HTTP, how could the
two protocols interoperate??
I guess moving an http server(e.g. Apache) with OStatus callback near
an xmpp sever(e.g. openfire).
I'm currently working on implementing OStatus in OSW. I am basically
extending the OSW openfire plugin functionality to support: webfinger,
pubsubhubub, salmon, etc.
I have already finished with Webfinger (still need to push a bit of
the code, the branch is called ostatus in github.com/onesocialweb) and
I'm working on publishing PuSH-enabled feeds for user's public
activities. Just watch the github repo to follow the progress.
I will probably move all OStatus-related functionality to another
Openfire plugin later, so a host can decide if he wants to support
both protocols or not. At the moment I'm just focusing on getting
OStatus to work.
Cheers,
Diana.
On Mar 19, 5:38 pm, Andrea Messina <messinand...@gmail.com> wrote:
> Since OSW is based on XMPP and OStatus is based on HTTP, how could the
> two protocols interoperate??
> I guess moving an http server(e.g. Apache) with OStatus callback near
> an xmpp sever(e.g. openfire).
If i understood, you are working on implementing OSTATUS XMPP
counterpart:
So Webfinger, PubSubHubbub, Salmon and ActivityStreams which work on
top of XMPP base protocol, like ONESOCIALWEB protocol does.
What about interoperability between HTTP and XMPP OSTATUS
interoperability?
On Mar 19, 7:37 pm, Diana Cheng <daianach...@googlemail.com> wrote:
> I'm currently working on implementing OStatus in OSW. I am basically
> extending the OSW openfire plugin functionality to support: webfinger,
> pubsubhubub, salmon, etc.
> I have already finished with Webfinger (still need to push a bit of
> the code, the branch is called ostatus in github.com/onesocialweb) and
> I'm working on publishing PuSH-enabled feeds for user's public
> activities. Just watch the github repo to follow the progress.
> I will probably move all OStatus-related functionality to another
> Openfire plugin later, so a host can decide if he wants to support
> both protocols or not. At the moment I'm just focusing on getting
> OStatus to work.
> Cheers,
> Diana.
> On Mar 19, 5:38 pm, Andrea Messina <messinand...@gmail.com> wrote:
> > Since OSW is based on XMPP and OStatus is based on HTTP, how could the
> > two protocols interoperate??
> > I guess moving an http server(e.g. Apache) with OStatus callback near
> > an xmpp sever(e.g. openfire).
> If i understood, you are working on implementing OSTATUS XMPP
> counterpart:
> So Webfinger, PubSubHubbub, Salmon and ActivityStreams which work on
> top of XMPP base protocol, like ONESOCIALWEB protocol does.
> What about interoperability between HTTP and XMPP OSTATUS
> interoperability?
> On Mar 19, 7:37 pm, Diana Cheng <daianach...@googlemail.com> wrote:
> > Hi Andrea,
> > I'm currently working on implementing OStatus in OSW. I am basically
> > extending the OSW openfire plugin functionality to support: webfinger,
> > pubsubhubub, salmon, etc.
> > I have already finished with Webfinger (still need to push a bit of
> > the code, the branch is called ostatus in github.com/onesocialweb) and
> > I'm working on publishing PuSH-enabled feeds for user's public
> > activities. Just watch the github repo to follow the progress.
> > I will probably move all OStatus-related functionality to another
> > Openfire plugin later, so a host can decide if he wants to support
> > both protocols or not. At the moment I'm just focusing on getting
> > OStatus to work.
> > Cheers,
> > Diana.
> > On Mar 19, 5:38 pm, Andrea Messina <messinand...@gmail.com> wrote:
> > > Since OSW is based on XMPP and OStatus is based on HTTP, how could the
> > > two protocols interoperate??
> > > I guess moving an http server(e.g. Apache) with OStatus callback near
> > > an xmpp sever(e.g. openfire).
Excuse me, but i have little kwnoledge about XMPP.
You said that you are implementing OStatus on Openfire that is an XMPP
server.
What about the HTTP callback used in the OStatus stack?
Are you developing a sort of OStatus gateway plugin for openfire??
Cheers,
Andrea
On Mar 20, 7:39 pm, Diana Cheng <daianach...@googlemail.com> wrote:
> Webfinger, PuSH, etc are HTTP-based protocols and that's what I am
> implementing. It just runs inside Openfire.
> Cheers,
> Diana.
> On Mar 19, 8:38 pm, Andrea Messina <messinand...@gmail.com> wrote:
> > If i understood, you are working on implementing OSTATUS XMPP
> > counterpart:
> > So Webfinger, PubSubHubbub, Salmon and ActivityStreams which work on
> > top of XMPP base protocol, like ONESOCIALWEB protocol does.
> > What about interoperability between HTTP and XMPP OSTATUS
> > interoperability?
> > On Mar 19, 7:37 pm, Diana Cheng <daianach...@googlemail.com> wrote:
> > > Hi Andrea,
> > > I'm currently working on implementing OStatus in OSW. I am basically
> > > extending the OSW openfire plugin functionality to support: webfinger,
> > > pubsubhubub, salmon, etc.
> > > I have already finished with Webfinger (still need to push a bit of
> > > the code, the branch is called ostatus in github.com/onesocialweb) and
> > > I'm working on publishing PuSH-enabled feeds for user's public
> > > activities. Just watch the github repo to follow the progress.
> > > I will probably move all OStatus-related functionality to another
> > > Openfire plugin later, so a host can decide if he wants to support
> > > both protocols or not. At the moment I'm just focusing on getting
> > > OStatus to work.
> > > Cheers,
> > > Diana.
> > > On Mar 19, 5:38 pm, Andrea Messina <messinand...@gmail.com> wrote:
> > > > Since OSW is based on XMPP and OStatus is based on HTTP, how could the
> > > > two protocols interoperate??
> > > > I guess moving an http server(e.g. Apache) with OStatus callback near
> > > > an xmpp sever(e.g. openfire).
