XMPP IM Client Design Guidelines
From XMPP WIKI
Revision as of 09:15, 13 May 2015 by
Flow
(
talk
|
contribs
)
(
diff
)
← Older revision
|
Latest revision
(
diff
) |
Newer revision →
(
diff
)
Jump to navigation
Jump to search
Contents
1
Introduction
2
Advices
2.1
Do not to split up JIDs into multiple input fields
2.1.1
Description
2.1.2
Rationale
2.2
Show user's room nickname and allow to change it
2.2.1
Description
2.2.2
Rationale
2.3
Use only TLS secured XMPP c2s connections
2.3.1
Description
2.3.2
Rationale
2.4
Do not to encode any semantic into the resource
2.4.1
Description
2.4.2
Rationale
2.5
Show the type of a remote source (mobile, pc, home, work, etc.) by means of Service Discovery and not the resource
2.5.1
Description
2.5.2
Rationale
Introduction
Advices
Do not to split up JIDs into multiple input fields
Description
Rationale
Show user's room nickname and allow to change it
Description
Rationale
Use only TLS secured XMPP c2s connections
Description
Rationale
Do not to encode any semantic into the resource
Description
Rationale
Show the type of a remote source (mobile, pc, home, work, etc.) by means of Service Discovery and not the resource
Description
Rationale
Navigation menu
Personal tools
Log in
Namespaces
Page
Discussion
Variants
expanded
collapsed
Views
Read
View source
View history
More
expanded
collapsed
Search
Navigation
Main page
Quickstart
Philosophy
Technology
FAQ
Software
Servers
Clients
Libraries
XSF Organization
Board of directors
Council
Work Teams
Communication
Editor
Infrastructure
Summits, Conferences & Meetups
Wiki
Recent changes
Help
Tools
What links here
Related changes
Special pages
Printable version
Permanent link
Page information