Le mardi 30 novembre 2004 � 09:28 +0000, Richard Dobson a �crit : > >> Ah ok then, well I would suggest you read up more on Jabber by reading > >> the > >> RFCs, JEPs etc > > > > I'm in the process of doing so, but notice: > > 1. There's much to read ; > > Yes but everyone here has had to do it at one time or another, and as I say > if you dont you will just end up wasting your time by doing things the wrong > way.
I'm not sure asking everyone to read everything to solve specific problems is really sound... > > Well, the patch I made for gaim is simple: you set an uri in your > > preferences, and it gets sent with your presence. So if you look at it > > this way, it's not dubious: it's just wrong. But if you consider the > > grand scheme of having the voip client able to notify that you're > > already on a call, or in do-not-disturb mode ; then really that's > > presence, and it's not so dubious. > > It is still very dubious IMO, presence is only intended for information that > all of your contacts will always be interested in (if its only useful for a > limited amount of your contacts then you need to be using pubsub), the fact > your are in a VoIP call is not going to be useful to many people, and if > this is all you are really using this for then its complete overkill and a > waste of bandwidth to tell other contacts the url of the call when its of no > use to them, all you really would need to do was change your presence to > "dnd" and "On the Phone", you are not supposed to be expressing > do-not-disturb with a VoIP extension since the presence stuff already has > "dnd" stuff built in. No: when I'm DnD for IM, then certainly I'm DnD for VoIP (also known as "away"). But when I'm in a voip call, I'm certainly still able to read IM messages: this is a presence information, and it can't be guessed from the IM presence. > > So in short: it really is presence, even if the sample implementation I > > have doesn't make it clear. > > Urm as you can see above its not really presence and it has not real use as > far as presence goes, as someone has already said your extension should be > in message or in iq and only sent specifically to people who need it, i.e. > people you are wanting to invite into a VoIP call. I'm not convinced it isn't presence, as discussed above. And since it is presence, I should be able to call my contact right away, not invite him/her. Just like once we accepted each other, we're able to send messages to each other right away... > >> So what I would suggest as your first step is read and try to understand > >> the > >> protocol layed out in the RFCs and the JEPs, and before you go creating > >> anything new double check the JEPs/RFCs to see if what you are trying to > >> do > >> has already been done or not, if it is at the development stages I would > >> suggest contacting the author of the JEPs in question and providing your > >> feedback on it to try and help out. > > > > I don't really want to develop on jabber ; I just want to be able to use > > it, and probably needs advice on this. > > If you dont want to develop then dont and leave this to someone who does, if > all you want to do is use VoIP with gaim then ask the gaim developers to add > this support into their client, they will then be able to integrate this > correctly and inline with jabber standards. I thought I had been precise enough: my main motivation is to develop some convenient and clean way to enable voip in gaim using jabber. Reading jabber documentation is a mean towards the goal, not the goal himself. I'm not saying "I don't want to develop". I think the jabber:x:oob trick is both standard -- and respects the spirit of what presence should be. JP _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mail.jabber.org/mailman/listinfo/jdev
