> > > > I've thought about this a great deal, and decided that the > > transport shouldn't make arbitrary routing decisions. I'm also > > thinking of where the messages get delivered to. > > It would make things less predictable. > > > > A better idea would be for client developers to make more sensible > > use of priorities. That is, if you set your client to available, it > > should make sure it has the highest priority. If it goes idle, set > > the priority lower. > > > > I believe some clients already do this. > > > > --- > > > > James > > Sorry if that came off a little more curtly than I meant it to :P > > --- > nah, I see your point, but in most ways I would guess if one resource is away and one is online, the online one should always be prioritized.
But this is a subject for discussion, I can see that. Also, there is probably a JEP or two that I should read before dwelling too deep into it :) -stian
