| Age | Commit message (Collapse) | Author |
|---|
|
BoostConnections no longer have their own thread, but are managed from
a central Boost IO thread instead.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Added the ability to set a default PayloadParserFactory.
Check factories in reverse order.
Add PayloadParserFactoryCollection unit test.
|
|
|
|
|
|
|
|
This is a utility class that can be used to easily trace incoming
and outgoing XML in bots etc.
|
|
|
|
|
|
|
|
|
|
|
|
Remko to review, please.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Only implemented PHOTO subtag, because it's the only thing we
need right now.
|
|
|
|
|
|
|
|
|
|
This should now be handled properly by using shared_ptrs.
|
|
|
|
|
|
XMPPRosterController now uses a RosterPushResponder to handle roster
pushes.
|
|
|
|
This can get us in all kinds of trouble, including that it makes it
impossible to use shared_ptr<> for Requests.
|
|
|
|
|
|
|
|
|
Swift