XmlStream should be convenient to use in a server context where there should be one authenticator per connection
|Reported by:||ralphm||Owned by:|
(github, coverage, patch, buildbot, log)
As the Jabber implementation has been mostly focussed on client side code (Jabber clients and Jabber components). The concept of authenticators has been used to initialize an XmlStream to the point that the connection can be used to exchange so-called XML stanzas. However, up to now, an already instantiated authenticator was passed to XmlStreamFactory, which in turn passes it to the XmlStream on instantiating in buildProtocol. This complicates using the same concept for server-side use, regarding #2320 and #3407.
This ticket attempts to change how authenticators get instantiated, by passing the authenticator class and its parameters to the factory, leaving it to the XmlStream instance to instantiate the authenticator. This makes adding a factory for accepting XML streams trivial.
Change History (19)
comment:13 Changed 8 years ago by glyph
- Summary changed from Refactor how Jabber authenticators get instantiated. to XmlStream should be convenient to use in a server context where there should be one authenticator per connection
comment:14 Changed 8 years ago by glyph
- Keywords review removed
- Owner changed from exarkun to ralphm