[JDEV] Jabber Client and presence ( using JabberBeans)

Richard Dobson richard at dobson-i.net
Tue Dec 3 10:58:57 CST 2002


You can do it but it is not part of the spec as far as I am aware, and even if you do do it, it is the same as <presence> so whats the point? It might even cause problems with some clients that are expecting no type for available presences.
  ----- Original Message ----- 
  From: Adrian Brown 
  To: jdev at jabber.org 
  Sent: Tuesday, December 03, 2002 3:03 PM
  Subject: Re: [JDEV] Jabber Client and presence ( using JabberBeans)


  Isn't it a type attribute of <presence> like unavailable?


  On Tuesday, December 3, 2002, at 02:51 pm, Richard Dobson wrote:


    There is no such type as "available" thats why it wont add it, the lack of a type means it is an availability packet.
     
    Richard 

    ----- Original Message -----
    From: Adrian Brown
    To: jdev at jabber.org
    Sent: Tuesday, December 03, 2002 2:30 PM
    Subject: [JDEV] Jabber Client and presence ( using JabberBeans)

    I'm trying to send a <presence> packet to another client (in my effort to avoid rosters - which are pointless for my client), In constructing
    the <presence> packet to send to a specified address, I've tried adding the type = 'available' but when I look at the debug, this is never sent or received. But the presence packet is:

    REC: <presence to="adrian2000 at jabber.org" from="adrianxp at jabber.org/work" id="p1"></presence>

    Anyone have any ideas?

    pb.reset();

    pb.setToAddress( UserJIDKit.getRemoteJID() );

    pb.setType( "available" );// this doesnt get added to the packet, can't work out why?

    pb.setIdentifier( "p1" );

    try {

    cb.send( pb.build() );

    System.out.println( "Subscribing" );

    }

    catch( InstantiationException e ) {

    System.out.println( "Could not subscribe" );

    }

    }

    Thanks!


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.jabber.org/jdev/attachments/20021203/ae4c0955/attachment-0002.htm>


More information about the JDev mailing list