[JDEV] About the protocol

[Chris Chen]

I am starting an Apache license-based Java client already (and it's not 
only for Jabber).

You can try taking a look at it at http://www.echomine.org/

It just started.. No code posted on the web, but the current alpha code is 
coming close to having a first release (alpha version).

Thanks,
Chris

At 12:35 AM 1/16/2002, you wrote:
>Hi German,
>
>Just curious. Are you going to release your code under an open-source
>licence? Actually, there are several OSS java client projects, but none are
>really finished products. Why don't all of you gather on the same project?
>
>Thanks
>
>Philippe Raxhon
>
>German Pablo de la Cruz wrote:
>      Thanks very muche Peter!.
>
>      I comment my case. I need to make a messenger with support to a
>      internal
>      protocol form my mates(I see in Jabber a good point). But today I need
>      communication to my clients to.
>
>      I don't have any problem to make bloking on the client side. But when
>      I
>      send an unavailable because of the previous presence, they see me for
>      a
>      glance.
>
>      I try to keep the block list in the server. But I don't know how!
>
>      Apart of that. I try to make messagin to MSN too. I see that sending
>      and
>      unavailable to a MSN buddy must result in a block. But it work only
>      with
>      all of the client (sending a presence without to:) I don't know if it
>      is
>      a bug or what.
>
>      Thanks again!
>
>      German
>
>
>           I'm implementing a Jabber client over Java, then I fault into two
>           problems
>
>                      1- How block a user like MSN Messenger.
>
>      Blocking communications from specific JIDs is usually done
>      client-side.
>      There is no Jabber protocol for this.
>
>                      2- How define a name to show in the roster of each
>           buddy that
>           see my presence.
>
>      When you add a roster item, you can include a 'name' attribute, like
>      so:
>
>      <iq type="set" id="uniquevalue">
>        <query xmlns="jabber:iq:roster">
>          <item jid="romeo at montague.net"
>              name="Romeo"
>              subscription="none"
>              ask="subscribe">
>            <group>friends</group>
>          </item>
>        </query>
>      </iq>
>
>      However, AFAIK there is no way to suggest to your "buddy" what that
>      name
>      attribute should include.
>
>      Peter
>
>
>      --__--__--
>
>      Message: 6
>      Date: Tue, 15 Jan 2002 09:51:10 -0800
>      To: jdev at jabber.org
>      From: Chris Chen <ckchris at idream.net>
>      Subject: Re: [JDEV] iq question
>      Reply-To: jdev at jabber.org
>
>      Technically, you should be giving each message (or ones that you're
>      waiting
>      on a reply for) a different ID rather than the same ID.  The way I do
>      it
>      is
>      to have a global ID counter that increments every time it is
>      called.  Jabber IM uses a string-based unique ID approach.  Any way
>      works
>      as long as the ID can be unique within your own context.
>
>      Thanks,
>      Chris
>
>      At 03:56 PM 1/14/2002, you wrote:
>           hello,
>
>           i was wondering if there is a way to send an id/key element to
>           the the
>      server
>           which the server will return in it's reply on a iq packet by
>           packet
>      basis.
>           basically, my concern is that some replies from the server simply
>      return
>           something like <iq type="result" id="1001"/> to signal a
>           successful iq
>           operation.  however, if i have different components listening for
>           iq
>      packets,
>           but in different contexts then it's not possible for my listeners
>           to
>      know
>           when the success signal was meant for them or not.  is there some
>           other
>           mechanism that i can use for this?
>
>           for a concrete example i have a listener that waits for the
>           return iq
>      packet
>           after authenticating, jabber:iq:auth, which returns  <iq type
>           ="result"
>           id="1001"/> for success and another listener that listens for iq
>      packets for
>           jabber:iq:private which can also return <iq type="result" id
>           ="1001"/>.
>      my
>           intent was for each listener to get both packets and to leave it
>           up to
>      the
>           listeners to filter out the packets their interested in.
>
>           any help with this would be appreciated.
>
>           zak.
>           _______________________________________________
>           jdev mailing list
>           jdev at jabber.org
>           http://mailman.jabber.org/listinfo/jdev
>
>      PGP at ldap://certserver.pgp.com/
>
>
>
>      --__--__--
>
>      _______________________________________________
>      jdev mailing list
>      jdev at jabber.org
>      http://mailman.jabber.org/listinfo/jdev
>
>
>      End of jdev Digest
>
>      _______________________________________________
>      jdev mailing list
>      jdev at jabber.org
>      http://mailman.jabber.org/listinfo/jdev
>
>
>
>_______________________________________________
>jdev mailing list
>jdev at jabber.org
>http://mailman.jabber.org/listinfo/jdev

PGP at ldap://certserver.pgp.com/