On Sat, Aug 26, 2006 at 02:20:22AM +0200, Sander Devrieze wrote: > Op vrijdag 25 augustus 2006 18:22, schreef Norman Rasmussen: > > On 8/25/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > You could parse the Message-Id of the email and use that as the xmpp > > > resource when authenticating your xmpp client. > > > > > > PID of the spawned process that parses the email will work as well.. but > > > someday you may want to run your program on more than one machine ;-) > > > > I hear /dev/random is a good alternative to handle this case. > > ...there still is change to have the same value twice. I think it is better > to > use [EMAIL PROTECTED] as resource. For example: [EMAIL PROTECTED]/[EMAIL > PROTECTED]
Perhaps I'm missing something obvious here, but why not use server generated resources? According to the RFC, any XMPP compliant server ought to make up a new resource identifier if you don't specify one when binding. Brian
