Welcome! Please
join the dialogue
.
Bohmian.org - Discussion - Treating all XMPP messages as chats
Bohmian Home
||
Dialogues
||
Pictures
||
Help
||
About Us
Most Recent Objects
Bistro du Midi
TAK Room
Embassy Suites Baltimore Hotel at BWI Airport Mayrland
ST3000DM001
Poetterization
Unix Philosophy
Poetterize
Random Objects
Netiquette violations
OpenDNS
IRS Free File
RFC 822
Sidney Crosby
Reverse Screening (TSA)
Open wireless networks
IMAP IDLE
The Matrix
SniqueAway.com
MicroB web browser
Extended warranties tend to cover the time of least-likely failure
Telestial customer support
Teoma
RFC 3921 section 2.1.1
Daisy Bell
WaterFire
Spike's Junkyard Dogs
Pig latin
Windows 7 Ballot Screen
Opera Unite
IPad identifies as a mobile device
VoIP to POTS gateway provider
Nokia N900 first impressions
Shutterfly
Associations
Connected Objects
Trying to update any application using the Maemo application catalog fails
I am not blocking Google messaging
I am blocking Google messaging
Userpage
Treat everything as an iPhone
Similarly Named
You should never restart your computer except as a last resort
Using Amazon as a Wedding Registry
MSIE objects implemented as separate windows
Treat everything as an iPhone
LibPurple based XMPP clients
Banning salt from all food
IPad identifies as a mobile device
XMPP Clients
Other User Entries
m
Treating all XMPP messages as chats
Rate this review:
[-]
[0]
[+]
My Opinion of
Treating all XMPP messages as chats
:
Dislike
Neutral
Like
m
posted November 05, 2009
RFC 3921 section 2.1.1
describes the type of messages that exist in standard
XMPP
(
Jabber
) conversations. The default type is a
normal
message, which is supposed to be processed similar to a standard
RFC 822
electronic mail
message.
It is
wrong
to treat this like a chat message, and
impolite
to simply lop off the
message subject
which appears to be the standard behaviour in
libPurple based XMPP clients
.