Skip to content

XMPP (RFC 6120), PubSub (XEP-0060) and Atom Over XMPP (RFC 4287) #535

@sjehuda

Description

@sjehuda

More detailed information: https://portal.mozz.us/gemini/woodpeckersnest.space/~schapps/journal/2024-12-09-atom-over-xmpp-for-news-readers.gmi

If you are not famiiliar with XMPP; XMPP (previously Jabber) is a
messaging system with open standards. XMPP is extensible via XEP.

I will discuss about XEP-0060: Publish-Subscribe.

Almost a couple of decades ago, a discussion2 arose about
incorporating Atom (RFC 4287) with XMPP PubSub, which is really easy
because both are XML data.

One of the major benefits of utilizing PubSub is native Push
Notifications (yes, that technique was much before HTML5) which do not
require HTTP pulling.

That would be a great feature to have photon to utilize XMPP PubSub
natively!

See a proof of concept3 I have made to parse PubSub nodes as Atom
Syndication Format.

Cheers,
Schimon
If you are not famiiliar with XMPP; XMPP (previously Jabber) is a
messaging system with open standards. XMPP is extensible via XEP.

I will discuss about XEP-0060: Publish-Subscribe.

Almost a couple of decades ago, a discussion1 arose about
incorporating Atom (RFC 4287) with XMPP PubSub, which is really easy
because both are XML data.

One of the major benefits of utilizing PubSub is native Push
Notifications (yes, that technique was much before HTML5) which do not
require HTTP pulling.

That would be a great feature to have photon to utilize XMPP PubSub
natively!

See a proof of concept2 I have made to parse PubSub nodes as Atom
Syndication Format.

Further more, I have made an HTTP gateway (Rivista XJP) which returns
XMPP PubSub nodes as Atom Syndication Format

Cheers,

Schimon

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions