Florian Jensen | 1 Sep 10:57
Gravatar

Re: jabberstudio.org

I could register it.

Greets,

Florian Jensen

On 01 Sep 2008, at 00:59, Peter Saint-Andre wrote:

> FYI, the jabberstudio.org domain is up for renewal, and the current  
> owner plans to let the registration lapse. If you want the domain,  
> please let me know and I'll tell the domain owner.
>
> /psa
> _______________________________________________
> JDev mailing list
> FAQ: http://www.jabber.org/discussion-lists/jdev-faq
> Forum: http://www.jabberforum.org/forumdisplay.php?f=20
> Info: http://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: JDev-unsubscribe <at> jabber.org
> _______________________________________________

_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________

(Continue reading)

Guenther Niess | 1 Sep 16:11
Picon
Favicon

Re: [Standards] Using Jabber in a KDE game

Hello Klaeg,

Kleag wrote:
> New to this list, I'm the author of KsirK, a KDE strategy game. Currently its 
> net game uses pure TCP/IP. One player start its game by setting a port on 
> which to listen to and the others connect to this port. Then the 
> libkdegames/kgame library is used to communicate. This lib as all what is 
> necessary to exchange messages including Qt objects. It also have a chat 
> framework. KsirK is a multiplayer game with, currently, does not allow passive 
> not playing participants.
> 
> Jabber seems to be a largely better solution. I want to have a very few 
> centralized system, keeping one client as the game server and using the 
> communication framework only for that: a communication tool. I'm also not 
> interested in controling cheating, basing the game in trust.
> 
> So, my idea is to progressively switch to Jabber. In a first step, it would 
> just allow to publish a proposed game in a kind of chat room and then the 
> current communication system would be used. In a second step, xmpp would also 
> be used to exchange game data.

For the first step you can use the service discovery (XEP-0030) and the
multi-user chat (XEP-0045).
Further on we suggest to use our multi-user gaming proposal [1] but this 
is still in development. This approach needs a server implementation for
the multi-user chat as well as for the game.  I'm currently working on a 
server plugin for openfire and would offer to support your efforts. 

It's also possible to integrate a small chat and gameserver in your game 
client implementation.
(Continue reading)

JLIST | 2 Sep 06:38
Picon

Communicate between two client instances of the same ID

Hi all, I'm new to the list.

I see an interesting application called gbridge (gbridge.com)
You run the app on multiple computers and login on them with
the same Google Talk ID, and from the app you can see other
computers' desktop and files. (I assume it's OK to mention
Google Talk here because it uses the jabber protocol.) So
essentially it uses Google Talk to send data back and forth.

Here's my question - I know you can login with the same ID
on multiple computers (I tried that with Google Talk) but does
XMPP provide a way to send data between two jabber client
instances of the same user ID? I'm still new to XMPP so
please bear with my ignorance. Any hint is appreciated.

Thanks,
jlist

_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________

Peter Saint-Andre | 2 Sep 06:54
Favicon

Re: Communicate between two client instances of the same ID

JLIST wrote:

> does XMPP provide a way to send data between two jabber client
> instances of the same user ID? 

Sure -- each client has a unique address differentiated by the XMPP 
resource identifier, so user <at> host/resource1 can exchange messages with 
user <at> host/resource2 and everyone is happy.

/psa
Attachment (smime.p7s): application/x-pkcs7-signature, 6751 bytes
_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________
JLIST | 2 Sep 07:31
Picon

Re: Communicate between two client instances of the same ID

Hello Peter,

Thanks for the prompt reply! I didn't know that.

A follow up question is, what would be the right element
of the protocol to use to send and receive custom data?
It'll be very helpful to me if someone can point me to
a link or some names that I can search for.

Thanks,
jlist

Monday, September 1, 2008, 9:54:48 PM, you wrote:

> JLIST wrote:

>> does XMPP provide a way to send data between two jabber client
>> instances of the same user ID? 

> Sure -- each client has a unique address differentiated by the XMPP 
> resource identifier, so user <at> host/resource1 can exchange messages with
> user <at> host/resource2 and everyone is happy.

> /psa

_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
(Continue reading)

Pedro Melo | 2 Sep 09:30
Favicon
Gravatar

Re: Communicate between two client instances of the same ID

Hi,

On Sep 2, 2008, at 6:31 AM, JLIST wrote:

> A follow up question is, what would be the right element
> of the protocol to use to send and receive custom data?
> It'll be very helpful to me if someone can point me to
> a link or some names that I can search for.

You can use two:

<message /> or <iq />.

the main difference is that <iq /> is a request/response dialog: you  
sen a <iq type="set"> or a <iq type="get"> and get back a <iq  
type="result"> or a <iq type="error">. The id attribute of the  
response matches the id of the request.

The <message /> is more of a send and forget about it style of  
communication.

Best regards,
--

-- 
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: melo <at> simplicidade.org
Use XMPP!

_______________________________________________
JDev mailing list
(Continue reading)

JLIST | 2 Sep 18:12
Picon

Re: Communicate between two client instances of the same ID

Thanks Pedro! Although <message /> doesn't get a reply,
I suppose its delivery is still guaranteed by the transport?
I'm thinking, <message /> sounds more efficient than <ip />
when relatively large amount of data needs to be transferred
because it doesn't require an XMPP level response.

>> A follow up question is, what would be the right element
>> of the protocol to use to send and receive custom data?
>> It'll be very helpful to me if someone can point me to
>> a link or some names that I can search for.

> You can use two:

> <message /> or <iq />.

> the main difference is that <iq /> is a request/response dialog: you
> sen a <iq type="set"> or a <iq type="get"> and get back a <iq  
type="result">> or a <iq type="error">. The id attribute of the  
> response matches the id of the request.

> The <message /> is more of a send and forget about it style of  
> communication.

_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________
(Continue reading)

Pedro Melo | 2 Sep 18:30
Favicon
Gravatar

Re: Communicate between two client instances of the same ID

Hi,

On Sep 2, 2008, at 5:12 PM, JLIST wrote:

> Thanks Pedro! Although <message /> doesn't get a reply,
> I suppose its delivery is still guaranteed by the transport?

No, unless you use http://www.xmpp.org/extensions/xep-0079.html and  
AFAIK no server supports that. So if you need reliability, I would use  
IQ for now.

> I'm thinking, <message /> sounds more efficient than <ip />

<iq />, not <ip />.

<ip /> gives me scary thoughts :)

> when relatively large amount of data needs to be transferred
> because it doesn't require an XMPP level response.

it wont be a huge overhead because the IQ response is tiny.

And IQ is 2 chars, MESSAGE is 7 :)

Best regards,

>
>
>>> A follow up question is, what would be the right element
>>> of the protocol to use to send and receive custom data?
(Continue reading)

Kevin Smith | 2 Sep 18:34
Picon

Re: Communicate between two client instances of the same ID

On Tue, Sep 2, 2008 at 5:30 PM, Pedro Melo <melo <at> simplicidade.org> wrote:
>> Thanks Pedro! Although <message /> doesn't get a reply,
>> I suppose its delivery is still guaranteed by the transport?
> No, unless you use http://www.xmpp.org/extensions/xep-0079.html and
> AFAIK no server supports that. So if you need reliability, I would use
> IQ for now.

I think it's http://www.xmpp.org/extensions/xep-0198.html you want for
guaranteed delivery, really, but equally no servers support that.
Server vendors: *poke*, it'd be great to see this being deployed, and
clients can't support it until servers do.

/K
_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________

Peter Saint-Andre | 2 Sep 18:37
Favicon

Re: Communicate between two client instances of the same ID

Kevin Smith wrote:
> On Tue, Sep 2, 2008 at 5:30 PM, Pedro Melo <melo <at> simplicidade.org> wrote:
>>> Thanks Pedro! Although <message /> doesn't get a reply,
>>> I suppose its delivery is still guaranteed by the transport?
>> No, unless you use http://www.xmpp.org/extensions/xep-0079.html and
>> AFAIK no server supports that. So if you need reliability, I would use
>> IQ for now.
> 
> I think it's http://www.xmpp.org/extensions/xep-0198.html you want for
> guaranteed delivery, really, but equally no servers support that.
> Server vendors: *poke*, it'd be great to see this being deployed, and
> clients can't support it until servers do.

That spec is under heavy revision. I'll try to push out a new version soon.

/psa

Attachment (smime.p7s): application/x-pkcs7-signature, 6751 bytes
_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________

Gmane