you're right. that was stupid. for now, i reverted the change and i will think about something.
regards, Gerolf On Sun, Apr 20, 2008 at 8:00 AM, Bernd Fondermann < [EMAIL PROTECTED]> wrote: > On Sun, Apr 20, 2008 at 12:59 AM, Gerolf Seitz <[EMAIL PROTECTED]> > wrote: > > hi bernd, > > > > in certain situations (eg probing presence information after initial > > presence, see RFC3921:5.1.1) > > it's necessary to get hold of the full JID. unfortunately it isn't > provided > > in the intial presence stanza > > sent from the client. > > > > while the resource is bound to the session in > > AbstractSessionContext#bindResource, it's not stored anywhere, > > it is stored, but not directly in the session. > > > so i was wondering whether #bindResource should reset the > initiatingEntity > > field to represent the full JID. > > no, because a session is not restricted to one bound resource! > > > i saw the methods ResourceRegistry#getBoundResources, but this seems to > be > > too much effort to > > finally get the resource identifier. > > can we make it less effort without storing this information twice? > where there is a SessionContext, there is the Resource Registry, too, > via ServerContext. > > > how about resetting the initialEntity field in > > AbstractSessionContext#bindResource ? > > (yes, next time i'll ask before committing :/ ) > > bad idea, I think, since it might gets overwritten from a second > resource binding. > > Bernd > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
