<div>Jon,</div> <div> </div> <div>        Did you implement in gtalk the external component protocol JEP ? Does gtalk accepts external components bindings ?</div> <div> </div> <div>        cya, mel<br><br> </div> <div><span class="gmail_quote">On 2/7/06, <b class="gmail_sendername">Jon Perlow</b> <<a href="mailto:perlow@gmail.com">perlow@gmail.com</a>> wrote:</span> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>I am a developer on Google Talk and Gmail. We are working on a JEP proposal and will send it out soon. <br><span class="sg"><br>-Jon</span> <div><span class="e" id="q_10945e6ae9d4232f_2"><br><br> <div><span class="gmail_quote">On 2/7/06, <b class="gmail_sendername">Peter Saint-Andre</b> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:stpeter@jabber.org" target="_blank">stpeter@jabber.org </a>> wrote:</span> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">-----BEGIN PGP SIGNED MESSAGE----- <br>Hash: SHA1<br><br>Remko Troncon wrote:<br>>> Not sure at all; it just looks vaguely like 0136 since it's <br>>> server-side, and it's possible for a client to disable the logging.<br>><br>> Well, it's not JEP-136 :-) All the client can do is enable/disable it, but <br>> the server does all the logging itself. This way, no matter what client you <br>> use to connect, your conversations gets logged, and you don't need to send your<br>> conversations over the wire twice either. <br>><br>> I like this idea actually, because it falls under the 'keep the client simple' <br>> principle. It's a lot easier than having to deal with concurrency, finding out<br>> which conversations belong together, submitting them to the server. It's safer <br>> as well (what if your connection or your client dies, and you didn't have a <br>> chance to commit your whole conversation), and it's incremental (a client needs<br>> to keep track of the whole conversation before it can submit it) <br><br>Yes, I chatted with one of the Google guys recently about this feature <br>(which is why I asked about server-side JEP-0136 stuff a week or two<br>ago). AFAIK this feature is something the client can enable or disable <br>on a per-contact basis ("don't log this conversation, please"). Also I <br>think this is something that would be supported (or not) by both servers<br>if the parties are on separate domains, so if I say "disable logging" my <br>server would ask the other server to do the same. But I'll let the <br>Google guys describe it more, since I don't know all the details.<br><br>Peter<br><br>- --<br>Peter Saint-Andre<br>Jabber Software Foundation<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.jabber.org/people/stpeter.shtml" target="_blank"> http://www.jabber.org/people/stpeter.shtml</a><br><br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.1 (Darwin)<br>Comment: Using GnuPG with Mozilla - <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://enigmail.mozdev.org/" target="_blank"> http://enigmail.mozdev.org</a> <br><br>iD8DBQFD6M1RNF1RSzyt3NURAqHCAJ4x1hynKvLy+CJBWLieS2w4kiFjDACfW6jN<br>jf1j8LsP6uF6KhuF7yQv/d4=<br>=UVen<br>-----END PGP SIGNATURE-----<br><br><br></blockquote></div><br></span></div></blockquote> </div><br><br clear="all"><br>-- <br>f u cn rd ths u cn b a gd prgmr !