Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Practical XMPP

You're reading from   Practical XMPP Unleash the power of XMPP in order to build exciting, realtime, federated applications based on open standards in a secure and highly scalable fashion

Arrow left icon
Product type Paperback
Published in Sep 2016
Publisher Packt
ISBN-13 9781785287985
Length 250 pages
Edition 1st Edition
Arrow right icon
Authors (3):
Arrow left icon
Steven Watkin Steven Watkin
Author Profile Icon Steven Watkin
Steven Watkin
David Koelle David Koelle
Author Profile Icon David Koelle
David Koelle
Lloyd Watkin Lloyd Watkin
Author Profile Icon Lloyd Watkin
Lloyd Watkin
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. An Introduction to XMPP and Installing Our First Server FREE CHAPTER 2. Diving into the Core XMPP Concepts 3. Building a One-on-One Chat Bot - The "Hello World" of XMPP 4. Talking XMPP in the Browser Using XMPP-FTW 5. Building a Multi-User Chat Application 6. Make Your Static Website Real-Time 7. Creating an XMPP Component 8. Building a Basic XMPP-Based Pong Game 9. Enhancing XMPPong with a Server Component and Custom Messages 10. Real-World Deployment and XMPP Extensions

Introducing the Jabber ID

In order to identify a user on the XMPP network, you need to know two things: the server on which they have an account and the account name on that server. So far, looks very much like an e-mail address, for example, marty@mcfly.fam.

However, XMPP being somewhat visionary for its time-realized that people would probably be using multiple devices/clients connected to the same account, and therefore added the resource that identifies a specific client connection on that account. When we include the resource, we get what is known as a full Jabber ID, or full JID. An example is marty@mcfly.fam/highschool.

The JID is made up of three parts:

Local

Domain

Resource

marty

@

mcfly.fam

/

highschool

Like e-mail, the domain part of the JID is case insensitive, but, unlike e-mail, the local part is also case-insensitive. XMPP goes one big step beyond this, however, and uses full Unicode for addressing so that JID can be made up of any number of non-ASCII characters...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image