Changes made to ProviderManager
Problem: we have to register the namespace with ProviderManager to receive IQs with that namepsace. However, on the server, we don't care about the namespace - that is the applications concern. We just want the IQ.
Solution A: Change providerManager to use a
DOMIQProviderwhenever nothing else is available.- up
- simpler for me.
- down
- may break other parts of my code in new and interesting ways. (update: it doesn't)
- almost definitely breaks packetRouter? (update: it doesn't)
Solution B: Register namespaces within the application.
- up:
- more humane to the Smack API.
- less testing for me.
- down
- One more &^%$ method in the framework. therefore, more testing.
- has to be done client-side via ECMAScript method
Solution C: Make application writers register their own handlers.
- up:
- easier for me
- we can remove the need to do this later fairly seamlessly, if we want to.
- down
- it's not something they should have to do for now.
- has to be done client-side via ECMAScript method
This has to be done on the client as well as the server. (B) doesn't work client-side.
(C) requires another method in ECMAScript.
Chosen solution: A. Added setDefaultIQProvider to ProviderManager.
© 2006. Some rights reserved. Author: Ian Sollars.
