[JDEV] Problem with agents-reply

[Thomas Muldowney]

Because the agents design in general sucks.  This is on our list of things to
fix, as a matter of fact the replacement idea is already been discussed.  It's
called browsing, should see more about it shortly.

--temas

On Sun, Oct 22, 2000 at 03:11:45PM +0200, Jens Askengren wrote:
> Hello!
> 
> A jabber client has to request the agent-list before requesting the roster 
> to be able to know the difference between JIDs of buddies and JIDs of 
> agents, right?
> 
> But there is a major problems with the current design of the agents reply:
> If the client request info about subagents, and get no response, it will 
> wait forever for a response. (Unless you do some hackish timeout tricks.)
>  
> Why not just make the agents reply expanded to include _all_ agents and
> subagents, since you'll have to request subagents recursively anyway?
> 
> Something like this would simplify client design a lot:
> 
> <iq type="result" id="1001">
> 	<query xmlns="jabber:iq:agents">
>  		<agent jid="rss.denmark">
> 			<name>Headline service</name>
> 			[...]
> 			<agent jid="freshmeat.rss.denmark">
> 				<name>Fresmeat news</name>
> 				[...]
> 			</agent>
> 		</agent>
>        		<agent jid="aim.denmark">
> 			[...]
> 		</agent>
> 	</query>
> </iq>
> 
> 	-Jens
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20001022/fcfbda68/attachment-0002.pgp>