But I believe, checks can be made directly from the UI instead of from the config file; if the connections are successful are not. Also, maybe I guess, a plugin can be handy in handling some error exceptions too!
I don't know much about how it will affect in a broader way for whether its in the core system or not! So, in the 1.0 version, the XMPP is out of the core right! On Fri, Mar 5, 2010 at 6:30 PM, Brion Vibber <br...@status.net> wrote: > On 03/05/2010 03:13 PM, Amit Rampurkar wrote: > >> Actually, last year when I was implementing XMPP for my site, I had a lot >> of issues with configurations. So, Brian had said that with a plug-in >> interface this would get cleaned up so that it will become easier to >> configure XMPP and use it. I haven't got a chance yet to look at the new >> plugin. I will check it out soon and see more of it! :-) >> I guess, my main issue was just about the configuration of the XMPP and >> verifying if those are correct or not. Guess, we will have this >> functionality in the plugin-able interface... >> > > I'm afraid breaking the code out to a plugin won't have any affect on the > ease of configuration. Giving it an administrative UI might -- but that's > completely unrelated to whether it's a plugin or not. > > -- brion vibber (brion @ status.net) > > _______________________________________________ > StatusNet-dev mailing list > StatusNet-dev@lists.status.net > http://lists.status.net/mailman/listinfo/statusnet-dev > -- _______________________________ ThankZ n RegardZ --> ~~ || AmiT <aka> p...@ppu || ~~ _______________________________ email: yOu hAVe it cell: eMAiL me if yOu dONt hAVe it HaVe @ RoCkInG TiMe AhEaD...!! _______________________________
_______________________________________________ StatusNet-dev mailing list StatusNet-dev@lists.status.net http://lists.status.net/mailman/listinfo/statusnet-dev
