go-xmpp

Author	SHA1	Message	Date
Matt Goodall	c9c8526476	Separate stream creation from XMPP use (client, component, etc). The address of the server is not necessarily related to the JID, e.g. DNS SRV lookups, manual configuration, etc. Splitting them up means there's more control and flexibility over how things are put together. We can always add convenience funcs later, e.g. something like DialClient(jid, password), to handle the common case.	2012-07-08 23:33:37 +01:00
Matt Goodall	23aeb1fd68	Associate a JID with an XMPP instance. Client connections negotiate a bound resource JID with the server. The bound JID may be different from the one requested or even generated by the server. Component connections do not negotiate the bound JID but still have a specific JID associated with the stream.	2012-07-08 12:18:51 +01:00
Matt Goodall	678b9c48a1	Make Stream public again, so we actually get some documentation for it.	2012-07-06 14:29:15 +01:00
Matt Goodall	627364727e	The client and component connections are really just streams too. Only difference is how they're setup. After that, it's the common iq, message, presence stuff ... to come soon.	2012-07-06 11:47:15 +01:00
Matt Goodall	ad000735ff	Move flag vars out of main().	2012-07-06 11:15:51 +01:00
Matt Goodall	7cf14c4f35	Add component API and example.	2012-06-27 13:14:18 +01:00