From owner-jdev@jabber.org Mon Mar 1 08:32:15 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id IAA15694 for jdev-list; Mon, 1 Mar 1999 08:32:15 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from seagal.vest.msk.ru (mail.vest.msk.ru [194.186.210.35]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id IAA15691 for ; Mon, 1 Mar 1999 08:32:11 -0600 Received: by seagal.vest.msk.ru with Internet Mail Service (5.0.1458.49) id ; Mon, 1 Mar 1999 17:16:24 +0300 Message-ID: From: Stanislav Maximov To: "Jabber Mail List (E-mail)" Subject: [JDEV] Win32 Server Date: Mon, 1 Mar 1999 17:16:22 +0300 X-Priority: 3 X-Mailer: Internet Mail Service (5.0.1458.49) Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Hello, All! Is there any win32 server ready? I need one to test my BeOS client. (I have win95 and beos running machines). /Stas. From owner-jdev@jabber.org Mon Mar 1 10:18:58 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id KAA16113 for jdev-list; Mon, 1 Mar 1999 10:18:58 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from localhost (jeremie@localhost) by mondo.eppg.com (8.8.7/8.8.7) with SMTP id KAA16110 for ; Mon, 1 Mar 1999 10:18:56 -0600 Date: Mon, 1 Mar 1999 10:18:56 -0600 (EST) From: Jeremie X-Sender: jeremie@mondo.eppg.com To: "Jabber Mail List (E-mail)" Subject: Re: [JDEV] Win32 Server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org http://jabber.org/download/jabber_win32_servertest.zip It's just a quick port of the codebase using cygwin. On Mon, 1 Mar 1999, Stanislav Maximov wrote: > Hello, All! > > Is there any win32 server ready? I need one to test my BeOS > client. (I have win95 and beos running machines). > > /Stas. > From owner-jdev@jabber.org Mon Mar 1 14:15:42 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id OAA18047 for jdev-list; Mon, 1 Mar 1999 14:15:42 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from localhost (jeremie@localhost) by mondo.eppg.com (8.8.7/8.8.7) with SMTP id OAA18044 for ; Mon, 1 Mar 1999 14:15:40 -0600 Date: Mon, 1 Mar 1999 14:15:40 -0600 (EST) From: Jeremie X-Sender: jeremie@mondo.eppg.com To: jdev@jabber.org Subject: [JDEV] Progress, CVS and Expat Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I'm finally making some progress again, and just checked in Expat and some glue code for it. Tonight I'll be updating the code in jabberbox to use expat and testing it out fully. I've setup CVS to post checkins to a mailing list, if you're interested in watching patches being checked into CVS, OR you're interested in *using* the cvs repository for your code at some point(just ask), feel free to join: http://jabber.org/mailman/listinfo/cvs Also, as you see above, this new list is set up through mailman: http://www.list.org/ If everything goes well for the next week or so, and there are no complaints, I'm probably going to move THIS list over to mailman, so let me know if there are any objections to this. Jer From owner-jdev@jabber.org Tue Mar 2 13:25:37 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id NAA26778 for jdev-list; Tue, 2 Mar 1999 13:25:37 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from mail.xuma.com ([209.0.254.4]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id NAA26775 for ; Tue, 2 Mar 1999 13:25:33 -0600 Received: from devnull ([208.192.215.142]) by mail.xuma.com (8.8.7/8.8.8) with SMTP id LAA08838; Tue, 2 Mar 1999 11:20:44 -0800 Message-ID: <039301be64e2$b71955f0$8ed7c0d0@devnull.bip.com> From: "Scott Perrine" To: Subject: [JDEV] ECONNRESET check Date: Tue, 2 Mar 1999 11:27:30 -0800 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_038F_01BE649F.A8F48F50" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org This is a multi-part message in MIME format. ------=_NextPart_000_038F_01BE649F.A8F48F50 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0390_01BE649F.A8F48F50" ------=_NextPart_001_0390_01BE649F.A8F48F50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hey there Jabber-folks ... I have had a problem with my transport server crashing when a client is = killed without cleanly disconnecting from the socket first ... i.e. I = control-c the rug out from underneath the carpet of my client app, so it = doesn't get to send its logout message & do a socket close. The read() = call in io.c fails and h_err() kills my transport. A small little fix takes care of this for me ... so I thought I'd mail = it in & see if it helped out anyone else as well. io.c: diff io.c io.c.new 1a2 > #include 83c84,85 < h_err(nbytes,"read"); --- > if(errno !=3D = ECONNRESET) > = h_err(nbytes,"read"); This way if the connection was killed, then read() failing & returning = -1 lets us "drop the connection" (and the user session) cleanly on our = side. -------------------------------------------------------------------------= -------------------------------- Scott Perrine ph: 415.777.9641 Xuma Technologies LLC http://www.xuma.com World Class Engineering For E-Business -------------------------------------------------------------------------= -------------------------------- ------=_NextPart_001_0390_01BE649F.A8F48F50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hey there Jabber-folks ...
 
I have had a problem with my transport server crashing when a = client is=20 killed without cleanly disconnecting from the socket first ... i.e. I = control-c=20 the rug out from underneath the carpet of my client app, so it doesn't = get to=20 send its logout message & do a socket close.  The read() call = in io.c=20 fails and h_err() kills my transport.
 
A small little fix takes care of this for me ... so I thought I'd = mail it=20 in & see if it helped out anyone else as well.
 
io.c:
diff io.c io.c.new
1a2
> #include=20 <errno.h>
83c84,85
<      &n= bsp;           &nb= sp;           &nbs= p;            = ;   =20 h_err(nbytes,"read");
---
>    &nb= sp;           &nbs= p;            = ;            =      =20 if(errno !=3D=20 ECONNRESET)
>         =             &= nbsp;           &n= bsp;           &nb= sp;        =20 h_err(nbytes,"read");
 
This way if the connection was = killed, then=20 read() failing & returning -1 lets us "drop the = connection" (and=20 the user session) cleanly on our side.
 
--------------------------------------------------------------------= -------------------------------------
Scott=20 Perrine           =             &= nbsp;           &n= bsp;    =20 ph: 415.777.9641
Xuma Technologies=20 LLC           &nbs= p;          =20 http://www.xuma.com
World Class = Engineering=20 For=20 E-Business
-----------------------------------------------------------= ----------------------------------------------
------=_NextPart_001_0390_01BE649F.A8F48F50-- ------=_NextPart_000_038F_01BE649F.A8F48F50 Content-Type: text/x-vcard; name="Scott Perrine.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Scott Perrine.vcf" BEGIN:VCARD VERSION:2.1 N:Perrine;Scott FN:Scott Perrine ORG:Xuma Technologies TEL;WORK;VOICE:415.777.9641 TEL;WORK;FAX:415.777.2704 ADR;WORK:;;655 Fourth St;San Francisco;CA;94107 LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:655 Fourth St=3D0D=3D0ASan = Francisco, CA 94107 URL: URL:http://www.xuma.com EMAIL;PREF;INTERNET:sperrine@xuma.com REV:19990302T192730Z END:VCARD ------=_NextPart_000_038F_01BE649F.A8F48F50-- From owner-jdev@jabber.org Tue Mar 2 18:43:17 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id SAA27982 for jdev-list; Tue, 2 Mar 1999 18:43:17 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from olaf.nick.org (nkirsch@nicholas-kirsch2.ups.edu [209.181.136.247]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id SAA27979 for ; Tue, 2 Mar 1999 18:43:15 -0600 Received: from localhost (nkirsch@localhost) by olaf.nick.org (8.9.1/8.9.0) with SMTP id QAA15288 for ; Tue, 2 Mar 1999 16:44:49 -0800 Date: Tue, 2 Mar 1999 16:44:49 -0800 (PST) From: "Nicholas M. Kirsch" To: jdev@jabber.org Subject: Re: [JDEV] ECONNRESET check In-Reply-To: <039301be64e2$b71955f0$8ed7c0d0@devnull.bip.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Thanks, I added the fix to the sources. Everybody remember that you can grab and test the latest version of Jabber from the CVS tree with the following commands : cvs -d :pserver:anoncvs@jabber.org:/cvs login (There is no password, just hit enter.) cvs -d :pserver:anoncvs@jabber.org:/cvs co jabber cd jabber; configure; make Nick nkirsch@olaf.nick.org From owner-jdev@jabber.org Thu Mar 4 14:02:48 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id OAA07146 for jdev-list; Thu, 4 Mar 1999 14:02:48 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id OAA07143; Thu, 4 Mar 1999 14:02:41 -0600 Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id PAA22517; Thu, 4 Mar 1999 15:02:07 -0500 (EST) Received: from tarot.nhl02.us.ups.com ([10.94.34.20]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id PAA13659; Thu, 4 Mar 1999 15:02:07 -0500 (EST) From: "Thomas Charron" To: "Jabber Development" , Subject: [JDEV] RE: [CVS] cvs commit: jabber/jabber/jabberbox config.c config.x Date: Thu, 4 Mar 1999 15:24:14 -0500 Message-ID: <000301be667c$f8713860$14225e0a@tarot.nhl02.us.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 In-Reply-To: <199903041622.KAA06132@mondo.eppg.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org ! Keep 'em comming, baybee!! I'm holding off on expanding my client classes untill the protocol change. I'm also going to use expat to parse as well, so I also may reuse some of the command line client source.. ;-P -- Thomas Charron United Parcel Service Northeast Region IE Software Developer "Moving at the speed of a T3 Trunk Line!" > -----Original Message----- > From: cvs-admin@jabber.org [mailto:cvs-admin@jabber.org]On Behalf Of > jeremie@mondo.eppg.com > Sent: Thursday, March 04, 1999 11:22 AM > To: cvs@jabber.org > Subject: [CVS] cvs commit: jabber/jabber/jabberbox config.c config.x > > > jeremie 99/03/04 10:22:13 > > Modified: jabber/jabberbox config.c config.x > Log: > Started redoing jabberbox to use expat for XML parsing. > Done: loads config file > Todo: protocol parsing/changes > > Revision Changes Path > 1.2 +25 -32 jabber/jabber/jabberbox/config.c > > Index: config.c > =================================================================== > RCS file: /cvs/jabber/jabber/jabberbox/config.c,v > retrieving revision 1.1 > retrieving revision 1.2 > diff -u -r1.1 -r1.2 > --- config.c 1999/02/14 09:37:43 1.1 > +++ config.c 1999/03/04 16:22:13 1.2 > @@ -5,7 +5,8 @@ > int nbytes, f; > char buff[MAXMSG], *conf_data, *new, *old; > char *config = DEFAULT_CONFIG; > - tap tp = {NULL,NULL,0}; > + xpt *xpt, *next; > + char *buf = NULL; > char myname[MAXHOSTNAMELEN + 1]; > > if(jpair_getval(etc.arg,"-c") != NULL) > @@ -18,29 +19,31 @@ > { > DBUG("Failed reading configuration file",config) > }else{ > - conf_data = malloc(1); > - conf_data[0] = '\0'; > - while(1) > - { > - nbytes = read(f,buff,MAXMSG-1); > - if(nbytes <= 0) > - break; > - buff[nbytes] = '\0'; > - new = malloc(nbytes + strlen(conf_data) + 1); > - strcat(new,conf_data); > - strcat(new,buff); > - old = conf_data; > - conf_data = new; > - free(old); > - } > - DBUG("Read in config file",""); > - tp.h_tag = &config_handle_transports; > - tag_parse(&tp, conf_data, NULL); > + xpt = xpt_file(config); > > - if(jpair_getval(etc.transports, "jabberbox") != NULL) > + if(xpt != NULL) > { > - tp.h_tag = &config_handle_jabberbox; > - tag_parse(&tp, jpair_getval(etc.transports, > "jabberbox"), NULL); > + next = xpt->children; > + while(next != NULL) > + { > + if(next->type == XPT_TAG) > + { > + > if(strcmp(next->name,"jabberbox") == 0) > + { > + etc.vars = > xpt2jpair(next->children); > + }else{ > + buf = NULL; > + > while(next->children != NULL) > + { > + buf = > strgrow(buf,xpt2str(next->children),1,1); > + > next->children = next->children->next; > + } > + etc.transports = > jpair_new(etc.transports, next->name, buf, 0); > + free(buf); > + } > + } > + next = next->next; > + } > } > } > > @@ -54,15 +57,5 @@ > etc.vars = jpair_new(etc.vars, "listen", myname, 0); > } > > -} > - > -void config_handle_transports(tag *t, void *v) > -{ > - etc.transports = jpair_new(etc.transports, t->name, t->contents, 0); > -} > - > -void config_handle_jabberbox(tag *t, void *v) > -{ > - etc.vars = jpair_new(etc.vars, t->name, t->contents, 0); > } > > > > > 1.2 +7 -6 jabber/jabber/jabberbox/config.x > > Index: config.x > =================================================================== > RCS file: /cvs/jabber/jabber/jabberbox/config.x,v > retrieving revision 1.1 > retrieving revision 1.2 > diff -u -r1.1 -r1.2 > --- config.x 1999/02/14 09:37:43 1.1 > +++ config.x 1999/03/04 16:22:13 1.2 > @@ -1,15 +1,15 @@ > + > This config file is just an example, please modify to fit your > needs... only recognized tags are processed, so you can > type anywhere outside of them and not hurt anything. > > This is the main section used by jabberbox. > > /tmp/jabber.log > - > + > > > This section is passed on to the "jabber" transport when it connects. > @@ -17,12 +17,12 @@ > how your server will identify itself on the Internet. Put any > secondary names > your server might be addressed as in an alias tag. > > - your.host.name.com > + jabber.org > JABBER > localhost > - > + > > > /var/tmp/jabber.basic.cache > @@ -52,3 +52,4 @@ > Anything can be contained between the tags, it all gets passed > to the transport. > > > + > > > > > _______________________________________________ > cvs maillist - cvs@jabber.org > http://jabber.org/mailman/listinfo/cvs > From owner-jdev@jabber.org Thu Mar 4 16:34:11 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id QAA08355 for jdev-list; Thu, 4 Mar 1999 16:34:11 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from chimera.acm.jhu.edu (mail@chimera.acm.jhu.edu [128.220.223.63]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id QAA08352 for ; Thu, 4 Mar 1999 16:34:08 -0600 Received: from localhost (cklempay@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3/asi-redhat) with ESMTP id RAA28976 for ; Thu, 4 Mar 1999 17:34:06 -0500 Date: Thu, 4 Mar 1999 17:34:06 -0500 (EST) From: "Corbett J. Klempay" To: jdev@jabber.org Subject: [JDEV] Crypto left and right... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Ok, sorry for my lack of response for the past week or so, but I'm back now..._this weekend_ is when I have to write up the proposal for my crypto project (due Monday). So, I need to solidify what I am going to do for this project. A few things: - Getting around the whole export controls on crypto seems almost too sticky...perhaps I'd be better off implementing digital sig authentication while just leaving hooks for other (i.e. offshore) people to drop in 128-bit crypto. - It's an idea for me to just sort of develop it separately (while keeping Jabber and its design in mind) so that my grade is not tied to other factors (Jabber development) that I can't control too easily. - I could try and put in 40 bit (128 seems like a no chance) and apply for an export license...anyone know how easy (not easy) this is? Also, any further comments about what digital sig architectures are candidates would be greatly appreciated...and remember we need legally unencumbered ones. ------------------------------------------------------------------------------ Corbett J. Klempay Quote of the Week: http://www2.acm.jhu.edu/~cklempay "Fear not those who argue but those who dodge." ------------------------------------------------------------------------------ From owner-jdev@jabber.org Thu Mar 4 17:04:09 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id RAA08536 for jdev-list; Thu, 4 Mar 1999 17:04:09 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from olaf.nick.org (nkirsch@nicholas-kirsch2.ups.edu [209.181.136.247]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id RAA08533 for ; Thu, 4 Mar 1999 17:04:07 -0600 Received: from localhost (nkirsch@localhost) by olaf.nick.org (8.9.1/8.9.1) with ESMTP id PAA08511 for ; Thu, 4 Mar 1999 15:04:04 -0800 Date: Thu, 4 Mar 1999 15:04:04 -0800 (PST) From: "Nicholas M. Kirsch" To: jdev@jabber.org Subject: [JDEV] Public jabber server.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I'm going to be running a public jabber server on olaf.nick.org. Anyone who is developing clients or what not can use it, as well as anybody else. Let me know if anyone has any problems. Nick From owner-jdev@jabber.org Thu Mar 4 19:03:11 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id TAA09096 for jdev-list; Thu, 4 Mar 1999 19:03:11 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from mail1.desupernet.net (qmailr@mail1.desupernet.net [204.249.184.36]) by mondo.eppg.com (8.8.7/8.8.7) with SMTP id TAA09093 for ; Thu, 4 Mar 1999 19:03:09 -0600 Received: (qmail 12526 invoked from network); 5 Mar 1999 01:02:50 -0000 Received: from unknown (HELO imaginative.net) (208.170.178.63) by mail1.desupernet.net with SMTP; 5 Mar 1999 01:02:50 -0000 Message-ID: <36DF2DAB.7F7613EE@imaginative.net> Date: Thu, 04 Mar 1999 20:04:43 -0500 From: Zach Nelson Organization: Imaginative Entertainment X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: jdev@jabber.org Subject: [JDEV] New to group.. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I think you're all doing a great thing with the Jabber project. I'm just gonna sit back and observe and maybe do some recruiting *grin* .. keep up the good work! Regards, Zach Nelson Imaginative Entertainment TechWatch dot Net From owner-jdev@jabber.org Thu Mar 4 20:12:30 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id UAA09336 for jdev-list; Thu, 4 Mar 1999 20:12:30 -0600 Received: from ziggy.jeremie.com (jer@cscd-02-32.dialup.netins.net [209.152.71.161]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id UAA09333 for ; Thu, 4 Mar 1999 20:12:27 -0600 Received: from localhost (jer@localhost) by ziggy.jeremie.com (8.8.7/8.8.7) with ESMTP id UAA02166 for ; Thu, 4 Mar 1999 20:11:49 -0600 X-Authentication-Warning: ziggy.jeremie.com: jer owned process doing -bs Date: Thu, 4 Mar 1999 20:11:48 -0600 (EST) From: Jeremie To: jdev@jabber.org Subject: Re: [JDEV] New to group.. In-Reply-To: <36DF2DAB.7F7613EE@imaginative.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Thanks! Once I make just a little more progress with the code(get the new protocol and changes included) we can really start cranking on clients and transports, and hopefully by mid-summer have a seriously powerful public release :) Jer On Thu, 4 Mar 1999, Zach Nelson wrote: > I think you're all doing a great thing with the Jabber project. I'm just > gonna sit back and observe and maybe do some recruiting *grin* .. keep > up the good work! > > Regards, > > Zach Nelson > Imaginative Entertainment > TechWatch dot Net > From owner-jdev@jabber.org Fri Mar 5 12:16:28 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id MAA13081 for jdev-list; Fri, 5 Mar 1999 12:16:28 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id MAA13078 for ; Fri, 5 Mar 1999 12:16:25 -0600 Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id NAA13025 for ; Fri, 5 Mar 1999 13:15:54 -0500 (EST) Received: from tarot.nhl02.us.ups.com ([10.94.34.20]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id NAA29711 for ; Fri, 5 Mar 1999 13:15:53 -0500 (EST) From: "Thomas Charron" To: "Jabber Development" Subject: [JDEV] Web Snapshots Date: Fri, 5 Mar 1999 13:38:04 -0500 Message-ID: <000701be6737$4e0d28a0$14225e0a@tarot.nhl02.us.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I'm wondering, how often is the jabber_snap off the jabber.org web page updated? I just downloaded it, and noticed it doesn't yet have like the last day and a half of cvs updates.. (I can't access CVS from behind our corp. firewall) If anyone happens to know of a CGI script that will do a cvs checkout, zip it up and send it as a file, I'd love you longlong time.. ;-P -- Thomas Charron United Parcel Service Northeast Region IE Software Developer "Moving at the speed of a T3 Trunk Line!" From owner-jdev@jabber.org Fri Mar 5 12:34:05 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id MAA13221 for jdev-list; Fri, 5 Mar 1999 12:34:05 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from ins2.netins.net (ins2.netins.net [167.142.225.2]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id MAA13218 for ; Fri, 5 Mar 1999 12:34:03 -0600 Received: from worf.netins.net (jeremie@worf.netins.net [167.142.225.4]) by ins2.netins.net (8.8.7/8.8.7) with SMTP id MAA23714 for ; Fri, 5 Mar 1999 12:34:02 -0600 (CST) Date: Fri, 5 Mar 1999 12:34:01 -0600 (CST) From: Jeremie Miller To: Jabber Development Subject: Re: [JDEV] Web Snapshots In-Reply-To: <000701be6737$4e0d28a0$14225e0a@tarot.nhl02.us.ups.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org It's updated at midnight CST, so it didn't have a good deal of what I checked in around 2AM :) I'll go re-run the snapshot... done. Jer On Fri, 5 Mar 1999, Thomas Charron wrote: > I'm wondering, how often is the jabber_snap off the jabber.org web page > updated? I just downloaded it, and noticed it doesn't yet have like the > last day and a half of cvs updates.. (I can't access CVS from behind our > corp. firewall) > > If anyone happens to know of a CGI script that will do a cvs checkout, zip > it up and send it as a file, I'd love you longlong time.. ;-P > > -- > Thomas Charron > United Parcel Service > Northeast Region > IE Software Developer > "Moving at the speed of a T3 Trunk Line!" > From owner-jdev@jabber.org Wed Mar 10 13:32:26 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id NAA02889 for jdev-list; Wed, 10 Mar 1999 13:32:26 -0600 Received: from ziggy.jeremie.com (jer@cscd-02-12.dialup.netins.net [209.152.71.141]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id NAA02886 for ; Wed, 10 Mar 1999 13:32:23 -0600 Received: from localhost (jer@localhost) by ziggy.jeremie.com (8.8.7/8.8.7) with ESMTP id NAA12891 for ; Wed, 10 Mar 1999 13:33:44 -0600 X-Authentication-Warning: ziggy.jeremie.com: jer owned process doing -bs Date: Wed, 10 Mar 1999 13:33:44 -0600 (EST) From: Jeremie To: jdev@jabber.org Subject: [JDEV] More progress... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org In the current source tree I have Jabberbox rewritten using Expat as the XML parsing engine and using the new document-style protocol. I was planning on completing the Jabber transport by now, but the Flu that's been going around(again!) hit me hard this week. I'm just recovering and have started ripping into the Jabber transport sources. By this weekend I should have it put back together. Over the next week or two the codebase should reach a point where it can be built upon, transports, modules, and clients. I also have a whole batch of changes for the web site. Stay tuned for more! Jer From owner-jdev@jabber.org Wed Mar 10 14:00:38 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id OAA03043 for jdev-list; Wed, 10 Mar 1999 14:00:38 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from chimera.acm.jhu.edu (mail@chimera.acm.jhu.edu [128.220.223.63]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id OAA03039 for ; Wed, 10 Mar 1999 14:00:35 -0600 Received: from localhost (cklempay@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3/asi-redhat) with ESMTP id PAA08353 for ; Wed, 10 Mar 1999 15:00:23 -0500 Date: Wed, 10 Mar 1999 15:00:22 -0500 (EST) From: "Corbett J. Klempay" To: jdev@jabber.org Subject: [JDEV] proposal Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Hey all...well, I turned in my proposal for the crypto project to add stuff to Jabber. I'll post again later today when I copy the Word97 document to my website or something (in case you guys want to look at it). I ended up having to target authentication only (no encryption) so as to prevent me from having to deal with export bullshit. However, the infrstructure will have already been laid; someone will be able to add encryption (someone offshore, I suppose) without much difficulty; the key distribution will have already been put in place, so all that would need to be done would be to add a little library of symmetric algorithms (probably along the lines of Blowfish/Twofish...and some others...but ideally ones not under patent) to hook into these keys. ------------------------------------------------------------------------------ Corbett J. Klempay Quote of the Week: http://www2.acm.jhu.edu/~cklempay "Fear not those who argue but those who dodge." ------------------------------------------------------------------------------ From owner-jdev@jabber.org Wed Mar 10 14:21:54 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id OAA03177 for jdev-list; Wed, 10 Mar 1999 14:21:54 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from chimera.acm.jhu.edu (mail@chimera.acm.jhu.edu [128.220.223.63]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id OAA03174 for ; Wed, 10 Mar 1999 14:21:50 -0600 Received: from galtgulch (jonlin06.hilander.com [207.96.113.103]) by chimera.acm.jhu.edu (8.9.3/8.9.3/asi-redhat) with SMTP id PAA08518 for ; Wed, 10 Mar 1999 15:21:40 -0500 Message-Id: <4.1.19990310151653.00a93010@chimera.acm.jhu.edu> X-Sender: cklempay@chimera.acm.jhu.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 10 Mar 1999 15:17:19 -0500 To: jdev@jabber.org From: "Corbett J. Klempay" Subject: [JDEV] it's online Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org http://www2.acm.jhu.edu/~cklempay/other/cryptoproposal.doc From owner-jdev@jabber.org Wed Mar 10 18:56:37 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id SAA03983 for jdev-list; Wed, 10 Mar 1999 18:56:37 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from mail1.desupernet.net (qmailr@mail1.desupernet.net [204.249.184.36]) by mondo.eppg.com (8.8.7/8.8.7) with SMTP id SAA03980 for ; Wed, 10 Mar 1999 18:56:35 -0600 Received: (qmail 17143 invoked from network); 11 Mar 1999 00:56:09 -0000 Received: from unknown (HELO imaginative.net) (208.170.179.48) by mail1.desupernet.net with SMTP; 11 Mar 1999 00:56:09 -0000 Message-ID: <36E714E5.6BFEC8CA@imaginative.net> Date: Wed, 10 Mar 1999 19:57:09 -0500 From: Zach Nelson Organization: Imaginative Entertainment X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: jdev@jabber.org Subject: [JDEV] VooDoo3 Giveaway Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Hey guys, Just wanted to give you a heads-up in case anyone was interested. We're giving away 3 3DFX VooDoo3 3500 video accelerators cards this month. All you gotta do is sign up :) http://www.techwatch.net The search engine isn't live yet, but the contest is :) -Zach PS: Hey Jeremie did you get my mail regarding development? From owner-jdev@jabber.org Fri Mar 12 14:11:55 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id OAA13668 for jdev-list; Fri, 12 Mar 1999 14:11:55 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from mail.dataengines.com (mail.dataengines.com [208.209.48.6]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id OAA13665 for ; Fri, 12 Mar 1999 14:11:53 -0600 Received: from localhost (localhost [127.0.0.1]) by mail.dataengines.com (8.9.3/8.9.3) with ESMTP id MAA08713 for ; Fri, 12 Mar 1999 12:11:38 -0800 Date: Fri, 12 Mar 1999 12:11:38 -0800 (PST) From: Myron Davis To: Jabber Development Subject: Re: [JDEV] Web Snapshots In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org What is the anonymous CVS login password? On Fri, 5 Mar 1999, Jeremie Miller wrote: > It's updated at midnight CST, so it didn't have a good deal of what I > checked in around 2AM :) > > I'll go re-run the snapshot... done. > > Jer > > On Fri, 5 Mar 1999, Thomas Charron wrote: > > > I'm wondering, how often is the jabber_snap off the jabber.org web page > > updated? I just downloaded it, and noticed it doesn't yet have like the > > last day and a half of cvs updates.. (I can't access CVS from behind our > > corp. firewall) > > > > If anyone happens to know of a CGI script that will do a cvs checkout, zip > > it up and send it as a file, I'd love you longlong time.. ;-P > > > > -- > > Thomas Charron > > United Parcel Service > > Northeast Region > > IE Software Developer > > "Moving at the speed of a T3 Trunk Line!" > > > From owner-jdev@jabber.org Fri Mar 12 14:37:10 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id OAA13811 for jdev-list; Fri, 12 Mar 1999 14:37:10 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from ins3.netins.net (root@ins3.netins.net [167.142.225.3]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id OAA13808 for ; Fri, 12 Mar 1999 14:37:08 -0600 Received: from worf.netins.net (jeremie@worf.netins.net [167.142.225.4]) by ins3.netins.net (8.8.7/8.8.7) with SMTP id OAA18771 for ; Fri, 12 Mar 1999 14:37:03 -0600 Date: Fri, 12 Mar 1999 14:37:03 -0600 (CST) From: Jeremie Miller To: Jabber Development Subject: Re: [JDEV] Web Snapshots In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > What is the anonymous CVS login password? > If you use "anoncvs" as the username, you can enter anything as the password. CVSROOT=:pserver:anoncvs@jabber.org:/cvs Jer From owner-jdev@jabber.org Fri Mar 12 15:01:55 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id PAA14047 for jdev-list; Fri, 12 Mar 1999 15:01:55 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from mail.ups.edu (mail.ups.edu [192.124.98.111]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id PAA14044 for ; Fri, 12 Mar 1999 15:01:53 -0600 Received: from zrussell (f46.resnet.ups.edu [198.104.176.46]) by mail.ups.edu (8.9.1/8.8.8) with SMTP id NAA17674 for ; Fri, 12 Mar 1999 13:06:43 -0800 (PST) Message-ID: <002e01be6ccc$18d9aec0$2eb068c6@zrussell.redmond> From: "Zach Russell" To: "Jabber Development" Subject: [JDEV] WinClient Date: Fri, 12 Mar 1999 13:05:15 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Is the win32 client checked into CVS? From owner-jdev@jabber.org Fri Mar 12 15:14:28 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id PAA14201 for jdev-list; Fri, 12 Mar 1999 15:14:28 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from ins6.netins.net (ins6.netins.net [167.142.225.6]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id PAA14198 for ; Fri, 12 Mar 1999 15:14:26 -0600 Received: from worf.netins.net (jeremie@worf.netins.net [167.142.225.4]) by ins6.netins.net (8.8.7/8.8.7) with SMTP id PAA03326 for ; Fri, 12 Mar 1999 15:14:22 -0600 (CST) Date: Fri, 12 Mar 1999 15:14:22 -0600 (CST) From: Jeremie Miller To: Jabber Development Subject: Re: [JDEV] WinClient In-Reply-To: <002e01be6ccc$18d9aec0$2eb068c6@zrussell.redmond> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > Is the win32 client checked into CVS? Well, the test client source for unix will compile in a win32 environment, but is just a command line app. There was a win32 gui test client but it's not being maintained. The source for it is available, but the author suggests that anyone interested would find it easier to just start over. If anyone wants to start working on this, I can give them access to use CVS. The Jabber server should be back in shape and building sometime this weekend to start testing against again(using the _new_ protocol). Jer From owner-jdev@jabber.org Fri Mar 12 15:20:25 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id PAA14243 for jdev-list; Fri, 12 Mar 1999 15:20:25 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id PAA14240 for ; Fri, 12 Mar 1999 15:20:22 -0600 Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id QAA03609 for ; Fri, 12 Mar 1999 16:19:45 -0500 (EST) Received: from tarot.nhl02.us.ups.com ([10.94.34.20]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id QAA06272 for ; Fri, 12 Mar 1999 16:19:44 -0500 (EST) From: "Thomas Charron" To: Subject: RE: [JDEV] Web Snapshots Date: Fri, 12 Mar 1999 16:42:10 -0500 Message-ID: <000701be6cd1$2f889f00$14225e0a@tarot.nhl02.us.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: Importance: Normal Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I know this has already been responded to, but that seems like a mightly silly question to ask.. ;-P -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" > -----Original Message----- > From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of > Myron Davis > Sent: Friday, March 12, 1999 3:12 PM > To: Jabber Development > Subject: Re: [JDEV] Web Snapshots > > > What is the anonymous CVS login password? > > On Fri, 5 Mar 1999, Jeremie Miller wrote: > > > It's updated at midnight CST, so it didn't have a good deal of what I > > checked in around 2AM :) > > > > I'll go re-run the snapshot... done. > > > > Jer > > > > On Fri, 5 Mar 1999, Thomas Charron wrote: > > > > > I'm wondering, how often is the jabber_snap off the > jabber.org web page > > > updated? I just downloaded it, and noticed it doesn't yet > have like the > > > last day and a half of cvs updates.. (I can't access CVS > from behind our > > > corp. firewall) > > > > > > If anyone happens to know of a CGI script that will do a > cvs checkout, zip > > > it up and send it as a file, I'd love you longlong time.. ;-P > > > > > > -- > > > Thomas Charron > > > United Parcel Service > > > Northeast Region > > > IE Software Developer > > > "Moving at the speed of a T3 Trunk Line!" > > > > > > From owner-jdev@jabber.org Fri Mar 12 16:04:30 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id QAA14504 for jdev-list; Fri, 12 Mar 1999 16:04:30 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from chimera.acm.jhu.edu (mail@chimera.acm.jhu.edu [128.220.223.63]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id QAA14501 for ; Fri, 12 Mar 1999 16:04:28 -0600 Received: from galtgulch (jonlin06.hilander.com [207.96.113.103]) by chimera.acm.jhu.edu (8.9.3/8.9.3/asi-redhat) with SMTP id RAA15069 for ; Fri, 12 Mar 1999 17:04:24 -0500 Message-Id: <4.1.19990312165903.00a9de60@chimera.acm.jhu.edu> X-Sender: cklempay@chimera.acm.jhu.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 12 Mar 1999 16:59:54 -0500 To: jdev@jabber.org From: "Corbett J. Klempay" Subject: [JDEV] Anyone looked? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Anyone else have a chance to look at the authentication stuff at http://www2.acm.jhu.edu/~cklempay/other/cryptoproposal.doc From owner-jdev@jabber.org Fri Mar 12 16:09:59 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id QAA14553 for jdev-list; Fri, 12 Mar 1999 16:09:59 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from olaf.nick.org (nkirsch@nicholas-kirsch2.ups.edu [209.181.136.247]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id QAA14550 for ; Fri, 12 Mar 1999 16:09:53 -0600 Received: from localhost (nkirsch@localhost) by olaf.nick.org (8.9.1/8.9.1) with ESMTP id PAA00636 for ; Fri, 12 Mar 1999 15:11:11 -0800 Date: Fri, 12 Mar 1999 15:11:11 -0800 (PST) From: "Nicholas M. Kirsch" To: Jabber Development Subject: Re: [JDEV] WinClient In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org As soon as Jeremie reports that the _new_ protocol is working, I will rebuild the source on olaf.nick.org, and a public Jabber server will be available for any client testing. Currently the jabber server doesn't require actual authentication, so putting anything as the username and password will work. We need feedback! We gotta hammer on this thing in order to spot deficiencies and bugs.. :) Nick On Fri, 12 Mar 1999, Jeremie Miller wrote: > > > Is the win32 client checked into CVS? > > Well, the test client source for unix will compile in a win32 environment, > but is just a command line app. There was a win32 gui test client but > it's not being maintained. The source for it is available, but the author > suggests that anyone interested would find it easier to just start over. > > If anyone wants to start working on this, I can give them access to use > CVS. > > The Jabber server should be back in shape and building sometime this > weekend to start testing against again(using the _new_ protocol). > > Jer > From owner-jdev@jabber.org Fri Mar 12 17:59:21 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id RAA15001 for jdev-list; Fri, 12 Mar 1999 17:59:21 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from olaf.nick.org (nkirsch@nicholas-kirsch2.ups.edu [209.181.136.247]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id RAA14998 for ; Fri, 12 Mar 1999 17:59:19 -0600 Received: from localhost (nkirsch@localhost) by olaf.nick.org (8.9.1/8.9.1) with ESMTP id RAA00452 for ; Fri, 12 Mar 1999 17:00:38 -0800 Date: Fri, 12 Mar 1999 17:00:38 -0800 (PST) From: "Nicholas M. Kirsch" To: Jabber Development Subject: Re: [JDEV] WinClient In-Reply-To: <002e01be6ccc$18d9aec0$2eb068c6@zrussell.redmond> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org No, it's not. There is a link to the source under the clients section on the webpage. It is no loenger being maintained, and thus is out-of-date with regard to the current library. It would probably be best for you just to start from scratch. Nick On Fri, 12 Mar 1999, Zach Russell wrote: > Is the win32 client checked into CVS? > From owner-jdev@jabber.org Fri Mar 12 18:30:55 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id SAA15166 for jdev-list; Fri, 12 Mar 1999 18:30:55 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from chimera.acm.jhu.edu (mail@chimera.acm.jhu.edu [128.220.223.63]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id SAA15163 for ; Fri, 12 Mar 1999 18:30:50 -0600 Received: from galtgulch (jonlin06.hilander.com [207.96.113.103]) by chimera.acm.jhu.edu (8.9.3/8.9.3/asi-redhat) with SMTP id TAA15892 for ; Fri, 12 Mar 1999 19:30:46 -0500 Message-Id: <4.1.19990312192516.00ab0160@chimera.acm.jhu.edu> X-Sender: cklempay@chimera.acm.jhu.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 12 Mar 1999 19:26:18 -0500 To: jdev@jabber.org From: "Corbett J. Klempay" Subject: [JDEV] HTML version now Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I just had Word97 write out an HTML version of the proposal too...I don't know why it converted the background of the Visio figure in there to a blue sort of color, but oh well, it didn't wreck anything. It's at: http://www2.acm.jhu.edu/~cklempay/other/cryptoproposal.html From owner-jdev@jabber.org Mon Mar 15 10:37:41 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id KAA26623 for jdev-list; Mon, 15 Mar 1999 10:37:41 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from smtp.doruk.net.tr (smtp.doruk.net.tr [212.58.4.4]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id KAA26619 for ; Mon, 15 Mar 1999 10:37:34 -0600 Received: from doruk.net.tr (zeus.doruk.net.tr [212.58.4.10]) by smtp.doruk.net.tr (8.8.5/SCO5) with SMTP id SAA06019 for ; Mon, 15 Mar 1999 18:57:23 +0200 (TSI) Received: from l049.pri.ppp.doruk.net.tr by doruk.net.tr (SMI-8.6/SMI-SVR4) id SAA05676; Mon, 15 Mar 1999 18:31:27 +0200 Date: Mon, 15 Mar 1999 18:36:05 +0200 (EET) From: "Kemal 'Disq' Hadimli" X-Sender: disq@heart_of_gold.localdomain To: jdev@jabber.org Subject: [JDEV] cabbar page Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Hi. Put up a cabbar page (with index.html this time :P ) @ disq.bir.net.tr/cabbar ;) bye, disqk Microsoft is not the answer. Microsoft is the question. NO (or Linux) is the answer. From owner-jdev@jabber.org Mon Mar 15 12:49:27 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id MAA28526 for jdev-list; Mon, 15 Mar 1999 12:49:27 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id MAA28523 for ; Mon, 15 Mar 1999 12:49:22 -0600 Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id NAA23485 for ; Mon, 15 Mar 1999 13:48:29 -0500 (EST) Received: from tarot.nhl02.us.ups.com ([10.94.34.20]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id NAA04266 for ; Mon, 15 Mar 1999 13:48:28 -0500 (EST) From: "Thomas Charron" To: Subject: RE: [JDEV] WinClient Date: Mon, 15 Mar 1999 14:10:58 -0500 Message-ID: <001401be6f17$8ee29ee0$14225e0a@tarot.nhl02.us.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 In-Reply-To: X-MIMEOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Jeremie.. As I've said, I'll take up the reigns on a Win32 client. Go ahead and send me the information regarding CVS access. I'm going to have to read up on a CVS client for Win32, never used it on the Windows end before. In the meantime I can do checkins via my Linux servers shared directories.. ;-P Ain't samba grand.. -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" > -----Original Message----- > From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of > Jeremie Miller > Sent: Friday, March 12, 1999 4:14 PM > To: Jabber Development > Subject: Re: [JDEV] WinClient > > > > > Is the win32 client checked into CVS? > > Well, the test client source for unix will compile in a win32 environment, > but is just a command line app. There was a win32 gui test client but > it's not being maintained. The source for it is available, but the author > suggests that anyone interested would find it easier to just start over. > > If anyone wants to start working on this, I can give them access to use > CVS. > > The Jabber server should be back in shape and building sometime this > weekend to start testing against again(using the _new_ protocol). > > Jer > From owner-jdev@jabber.org Tue Mar 16 12:57:49 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id MAA08134 for jdev-list; Tue, 16 Mar 1999 12:57:49 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from homer.communities.com (homer.communities.com [205.162.51.9]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id MAA08130 for ; Tue, 16 Mar 1999 12:57:46 -0600 Received: from [205.162.51.192] (carlsmack.communities.com [205.162.51.192]) by homer.communities.com (8.9.1/8.9.1) with ESMTP id KAA15428 for ; Tue, 16 Mar 1999 10:59:38 -0800 Message-Id: <199903161859.KAA15428@homer.communities.com> X-Mailer: Microsoft Outlook Express for Macintosh - 4.0a (190) Date: Tue, 16 Mar 1999 10:59:54 -0800 Subject: [JDEV] New to project From: "Carl MacDonald" To: jdev@jabber.org Mime-version: 1.0 X-Priority: 3 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: 7bit Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Just wanted to say hello, introduce myself to the list, and ask a question :) I'm trying to build the latest 0.6 source (snap_921477600) on my Linux box (Red Hat 5.0) and the autoconf isn't processing the make files in the subdirectories correctly. I was wondering if this is a known problem and shouldn't bother spending anymore cycles trying to sort out what I did wrong. Thanks in advance -- Carl From owner-jdev@jabber.org Tue Mar 16 13:37:44 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id NAA08333 for jdev-list; Tue, 16 Mar 1999 13:37:44 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from ins6.netins.net (ins6.netins.net [167.142.225.6]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id NAA08330 for ; Tue, 16 Mar 1999 13:37:42 -0600 Received: from worf.netins.net (jeremie@worf.netins.net [167.142.225.4]) by ins6.netins.net (8.8.7/8.8.7) with SMTP id NAA08172 for ; Tue, 16 Mar 1999 13:37:40 -0600 (CST) Date: Tue, 16 Mar 1999 13:37:40 -0600 (CST) From: Jeremie Miller To: jdev@jabber.org Subject: Re: [JDEV] New to project In-Reply-To: <199903161859.KAA15428@homer.communities.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > Just wanted to say hello, introduce myself to the list, and ask a question > :) Hola! > I'm trying to build the latest 0.6 source (snap_921477600) on my Linux box > (Red Hat 5.0) and the autoconf isn't processing the make files in the > subdirectories correctly. I was wondering if this is a known problem and > shouldn't bother spending anymore cycles trying to sort out what I did > wrong. Well, the 0.6 stuff is in MAJOR flux right now... It's getting closer to release every day now, but it still has some major pieces to be hooked back up. As far as autoconf goes, I'm not having a problem but I don't know much about it. Nick put it in place and is gone on spring break this week, I'm sure he'll be able to help figure out what's up when he gets back. Thanks! Jer From owner-jdev@jabber.org Tue Mar 16 13:44:07 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id NAA08399 for jdev-list; Tue, 16 Mar 1999 13:44:07 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id NAA08395 for ; Tue, 16 Mar 1999 13:44:04 -0600 Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id OAA05795 for ; Tue, 16 Mar 1999 14:43:19 -0500 (EST) Received: from tarot.nhl02.us.ups.com ([10.94.34.20]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id OAA24906 for ; Tue, 16 Mar 1999 14:43:18 -0500 (EST) From: "Thomas Charron" To: Subject: RE: [JDEV] New to project Date: Tue, 16 Mar 1999 15:05:49 -0500 Message-ID: <000101be6fe8$631a0ce0$14225e0a@tarot.nhl02.us.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal In-Reply-To: <199903161859.KAA15428@homer.communities.com> Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I haven't myself looked at the snaps recently, but the core code in and of itself has been going thru a drastic change as we move (HAVE moved) to a new XML parser called expat. On another note, could you post exactly what errors you got just in case it is something not related to this? I'm guessing it has to do with one of the expat include files myself.. -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" > -----Original Message----- > From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of > Carl MacDonald > Sent: Tuesday, March 16, 1999 2:00 PM > To: jdev@jabber.org > Subject: [JDEV] New to project > > > Just wanted to say hello, introduce myself to the list, and ask a question > :) > > I'm trying to build the latest 0.6 source (snap_921477600) on my Linux box > (Red Hat 5.0) and the autoconf isn't processing the make files in the > subdirectories correctly. I was wondering if this is a known problem and > shouldn't bother spending anymore cycles trying to sort out what I did > wrong. > > Thanks in advance > -- > Carl > From owner-jdev@jabber.org Tue Mar 16 14:16:51 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id OAA08596 for jdev-list; Tue, 16 Mar 1999 14:16:51 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from homer.communities.com (homer.communities.com [205.162.51.9]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id OAA08593 for ; Tue, 16 Mar 1999 14:16:48 -0600 Received: from [205.162.51.192] (carlsmack.communities.com [205.162.51.192]) by homer.communities.com (8.9.1/8.9.1) with ESMTP id MAA17498 for ; Tue, 16 Mar 1999 12:18:21 -0800 Message-Id: <199903162018.MAA17498@homer.communities.com> X-Mailer: Microsoft Outlook Express for Macintosh - 4.0a (190) Date: Tue, 16 Mar 1999 12:18:37 -0800 Subject: Re: [JDEV] New to project From: "Carl MacDonald" To: jdev@jabber.org Mime-version: 1.0 X-Priority: 3 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: 7bit Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org ---------- >From: "Thomas Charron" >To: >Subject: RE: [JDEV] New to project >Date: Tue, Mar 16, 1999, 12:05 PM > > I haven't myself looked at the snaps recently, but the core code in and of >itself has been going thru a drastic change as we move (HAVE moved) to a new >XML parser called expat. > > On another note, could you post exactly what errors you got just in case it >is something not related to this? I'm guessing it has to do with one of the >expat include files myself.. > >-- >Thomas Charron >United Parcel Service >Northeast Region >"Moving at the speed of a T3 Trunk Line!" > > Ok, here it is. Configure goes through with no problem, but when you make, you find that the makefiles in the subdirectories didn't get all of the variables (@SHELL@ most notably). -- Carl cd . && aclocal cd . && automake --gnu Makefile cd . && autoconf /bin/sh ./config.status --recheck running /bin/sh ./configure --no-create --no-recursion loading cache ./config.cache checking for a BSD compatible install... (cached) /usr/bin/install -c checking whether build environment is sane... yes checking for working aclocal... found checking for working autoconf... found checking for working automake... found checking for working autoheader... found checking for working makeinfo... found checking whether make sets ${MAKE}... (cached) yes checking for gcc... (cached) gcc checking whether the C compiler (gcc ) works... yes checking whether the C compiler (gcc ) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking whether gcc accepts -g... (cached) yes checking for c++... (cached) c++ checking whether the C++ compiler (c++ ) works... yes checking whether the C++ compiler (c++ ) is a cross-compiler... no checking whether we are using GNU C++... (cached) yes checking whether c++ accepts -g... (cached) yes checking for bison... (cached) bison -y ./configure: AM_PROG_LEX: command not found ./configure: AM_PROG_LIBTOOL: command not found checking for mawk... (cached) gawk checking for ranlib... (cached) ranlib checking for a BSD compatible install... /usr/bin/install -c checking how to run the C preprocessor... (cached) gcc -E checking for ANSI C header files... (cached) yes checking for pthread_create in -lpthread... (cached) yes creating ./config.status cd . \ && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status creating Makefile cd . && autoheader cd . \ && CONFIG_FILES= CONFIG_HEADERS=config.h \ /bin/sh ./config.status creating config.h make all-recursive make[1]: Entering directory `/drive2/home/scots/jabber_source/jabber_snap_921477600' Making all in lib make[2]: Entering directory `/drive2/home/scots/jabber_source/jabber_snap_921477600/lib' cd .. \ && CONFIG_FILES=lib/Makefile CONFIG_HEADERS= /bin/sh ./config.status creating lib/Makefile make[2]: Leaving directory `/drive2/home/scots/jabber_source/jabber_snap_921477600/lib' make[2]: @SHELL@: Command not found make[2]: Entering directory `/drive2/home/scots/jabber_source/jabber_snap_921477600/lib' make[2]: Entering directory `/drive2/home/scots/jabber_source/jabber_snap_921477600/lib' make[2]: @SHELL@: Command not found make[2]: *** [all-recursive] Error 127 make[2]: Leaving directory `/drive2/home/scots/jabber_source/jabber_snap_921477600/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/drive2/home/scots/jabber_source/jabber_snap_921477600' make: *** [all-recursive-am] Error 2 From owner-jdev@jabber.org Tue Mar 16 14:29:51 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id OAA08689 for jdev-list; Tue, 16 Mar 1999 14:29:51 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from baal.visi.com (baal.visi.com [209.98.98.3]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id OAA08686 for ; Tue, 16 Mar 1999 14:29:49 -0600 Received: from isis.visi.com (hackel@isis.visi.com [209.98.98.8]) by baal.visi.com (8.8.8/8.7.5) with SMTP id OAA16265 for ; Tue, 16 Mar 1999 14:29:48 -0600 (CST) Posted-Date: Tue, 16 Mar 1999 14:29:48 -0600 (CST) Date: Tue, 16 Mar 1999 14:29:35 -0600 (CST) From: Ryan Hayle To: jdev@jabber.org Subject: [JDEV] Win32 Client Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I guess I never got added to the devel list a while back, so here I am again.. I just wanted to say that I've done some very preliminary work on a win32 client, and I hope to speed things up and get something to show in a week or so (spring break). Especially if I can get Visual Studio to run under Virtual Platform (linux). :) Anyways, since it seems no one is still working on this, I'll continue.. If anyone has comments, suggestiomns, let me know, but I'm just giving it a basic ICQish look right now. On a side note, has any progress/work been done on the plugins for ICQ/AIM/etc. networks? I think that's how I remember things like that working. I'd be interested in that as well. EMYL, Hackel From owner-jdev@jabber.org Tue Mar 16 16:07:40 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id QAA09071 for jdev-list; Tue, 16 Mar 1999 16:07:40 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id QAA09066 for ; Tue, 16 Mar 1999 16:07:35 -0600 Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id RAA06453 for ; Tue, 16 Mar 1999 17:06:54 -0500 (EST) Received: from tarot.nhl02.us.ups.com ([10.94.34.20]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id RAA23051 for ; Tue, 16 Mar 1999 17:06:49 -0500 (EST) From: "Thomas Charron" To: Subject: RE: [JDEV] Win32 Client Date: Tue, 16 Mar 1999 17:29:24 -0500 Message-ID: <000001be6ffc$71c91d80$14225e0a@tarot.nhl02.us.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal In-Reply-To: Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Alrighty.. A couple questions.. First would be how far along is your current client code wise? Are the protocols hard coded, or have you done some work on having them centralized as resources or something.. I also am working on reworking my windows client, mostly just getting the backend stuff sturdy so it can take a beating. Can you send me what you have now so I can take a look at it? Also, if you manage to get Visual Studio working under Wine, PLEASE let me know.. I haven't tried becouse I figured it'd either be painfully slow or virtually impossible.. -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" > -----Original Message----- > From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of > Ryan Hayle > Sent: Tuesday, March 16, 1999 3:30 PM > To: jdev@jabber.org > Subject: [JDEV] Win32 Client > > > I guess I never got added to the devel list a while back, so here I am > again.. I just wanted to say that I've done some very preliminary work on > a win32 client, and I hope to speed things up and get something to show in > a week or so (spring break). Especially if I can get Visual Studio to run > under Virtual Platform (linux). :) Anyways, since it seems no one is > still working on this, I'll continue.. If anyone has comments, > suggestiomns, let me know, but I'm just giving it a basic ICQish look > right now. > > On a side note, has any progress/work been done on the plugins for > ICQ/AIM/etc. networks? I think that's how I remember things like that > working. I'd be interested in that as well. > > EMYL, > Hackel > From owner-jdev@jabber.org Tue Mar 16 20:46:35 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id UAA09853 for jdev-list; Tue, 16 Mar 1999 20:46:35 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from spartacus.hula.net (root@spartacus.hula.net [206.127.232.5]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id UAA09849 for ; Tue, 16 Mar 1999 20:46:32 -0600 Received: from sculdheizo (halau28.hula.net [206.127.234.220]) by spartacus.hula.net (8.9.0/8.9.0) with SMTP id QAA04348 for ; Tue, 16 Mar 1999 16:46:06 -1000 (HST) Message-ID: <001a01be7020$8b9ae080$dcea7fce@sculdheizo> From: "Donovan Schulteis" To: Subject: Re: [JDEV] Win32 Client Date: Tue, 16 Mar 1999 16:47:48 -1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > Also, if you manage to get Visual Studio working under Wine, PLEASE let me >know.. I haven't tried becouse I figured it'd either be painfully slow or >virtually impossible.. Please post that! Enquiring minds want to know!! :) It's probably the only real reason I'm still using Win! Deej From owner-jdev@jabber.org Tue Mar 16 22:09:31 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id WAA10102 for jdev-list; Tue, 16 Mar 1999 22:09:31 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from mw1.texas.net (mw1.texas.net [206.127.30.11]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id WAA10099 for ; Tue, 16 Mar 1999 22:09:28 -0600 Received: from tcnet03-087.houston.texas.net (tcnet03-087.houston.texas.net [209.99.82.150]) by mw1.texas.net (2.4/2.4) with ESMTP id WAA09255 for ; Tue, 16 Mar 1999 22:09:27 -0600 (CST) Date: Tue, 16 Mar 1999 22:09:32 -0600 (EST) From: Eliot Landrum X-Sender: eliot@montague.verona To: jdev@jabber.org Subject: [JDEV] (nt) Virtual Machine under Linux In-Reply-To: <001a01be7020$8b9ae080$dcea7fce@sculdheizo> Message-ID: Organization: http://lonestar.texas.net/~landrum/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Supposedly people are having pretty good success with the vmware beta under Linux. It makes a virtual machine for Windows (or any other OS from what I understand). Slashdot posted the announcement for the vmware beta for Linux yesterday. Sorry for the off topic post here, just thought ya'll might be interested in case WINE doesn't work out. Eliot Landrum elandrum@bigfoot.com On Tue, 16 Mar 1999, Donovan Schulteis wrote: > > Also, if you manage to get Visual Studio working under Wine, PLEASE let me > >know.. I haven't tried becouse I figured it'd either be painfully slow or > >virtually impossible.. > > > Please post that! Enquiring minds want to know!! :) > It's probably the only real reason I'm still using Win! > > Deej From owner-jdev@jabber.org Wed Mar 17 09:17:24 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id JAA11982 for jdev-list; Wed, 17 Mar 1999 09:17:24 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from raystewart.com (shiblon.lightrealm.com [209.203.232.4]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id JAA11978 for ; Wed, 17 Mar 1999 09:17:21 -0600 Received: from hawthorne (hil-c45-005-vty172.as.wcom.net [206.175.196.172]) by raystewart.com (8.8.7/8.8.5) with SMTP id HAA09599 for ; Wed, 17 Mar 1999 07:17:46 -0800 (PST) Message-ID: <003d01be7089$9d3f62c0$1e04a8c0@na.com> From: "Dave Smith" To: Subject: *Offsubject* [JDEV] Win32 Client Date: Wed, 17 Mar 1999 09:19:50 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0810.800 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > Also, if you manage to get Visual Studio working under Wine, PLEASE let me >know.. I haven't tried becouse I figured it'd either be painfully slow or >virtually impossible.. You're not far from the truth -- it's practically impossible. However, you might consider trying out VMware for Linux (www.vmware.com) I've been testing it and have managed to get NT4-SP3 w/ MS Office 97 running very smoothly in a X-window (which is quite a high, let me tell you!) :) Something to consider... :) D. From owner-jdev@jabber.org Sat Mar 20 13:29:29 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id NAA28419 for jdev-list; Sat, 20 Mar 1999 13:29:29 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from gulf.csc.UVic.CA (gulf.csc.UVic.CA [142.104.105.200]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id NAA28416 for ; Sat, 20 Mar 1999 13:29:27 -0600 From: qbradley@csc.UVic.CA Received: from valdes.csc.UVic.CA (valdes.csc.UVic.CA [142.104.105.203]) by gulf.csc.UVic.CA (8.8.8/8.8.8) with SMTP id LAA21032 for ; Sat, 20 Mar 1999 11:29:20 -0800 (PST) Received: from localhost by valdes.csc.UVic.CA (SMI-8.6/SMI-SVR4) id LAA00319; Sat, 20 Mar 1999 11:29:18 -0800 Date: Sat, 20 Mar 1999 11:29:17 -0800 (PST) X-Sender: qbradley@valdes To: jdev@jabber.org Subject: [JDEV] New protocol specs? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Is the new protocol documented anywhere? I'll start digging through the sources to try and figure out how exactly it has changed but would prefer to just have that information :-) btw, with snapshopt_921909600 I fail to compile the client, there seems to be missing a definition of "tag" structure. This structure might have been part of the old parsing code. Has the client not yet been updated to use expat? 24 ~/jabber/jabber_snap_921909600/clients $ make Making all in jabber make[1]: Entering directory `/home/qbradley/jabber/jabber_snap_921909600/clients/jabber' gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I ../../lib/ -g -O2 -c lib_deliver.c In file included from jabber.h:15, from lib_deliver.c:1: defs.h:2: warning: `VERSION' redefined ../../config.h:17: warning: this is the location of the previous definition In file included from jabber.h:17, from lib_deliver.c:1: functions.h:5: parse error before `*' functions.h:7: parse error before `*' functions.h:8: parse error before `*' functions.h:9: parse error before `*' functions.h:10: parse error before `*' functions.h:11: parse error before `*' followed by some warnings about casting a pointer to an integer without a cast. Quetzalcoatl Bradley qbradley@csc.uvic.ca From owner-jdev@jabber.org Mon Mar 22 00:12:18 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id AAA01325 for jdev-list; Mon, 22 Mar 1999 00:12:18 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from localhost (jeremie@localhost) by mondo.eppg.com (8.8.7/8.8.7) with SMTP id AAA01322 for ; Mon, 22 Mar 1999 00:12:16 -0600 Date: Mon, 22 Mar 1999 00:12:16 -0600 (EST) From: Jeremie X-Sender: jeremie@mondo.eppg.com To: jdev@jabber.org Subject: Re: [JDEV] New protocol specs? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > > Is the new protocol documented anywhere? I'll start digging through the > sources to try and figure out how exactly it has changed but would prefer > to just have that information :-) It's not officially up on the site yet, but you can get a preview here: http://jabber.org/developers/archive/9902/msg00006.html After I bring the code up to date with the proposals(this week, almost ready), I'm going to be seriously updating the docs and web site. > btw, with snapshopt_921909600 I fail to compile the client, there seems to > be missing a definition of "tag" structure. This structure might have > been part of the old parsing code. Has the client not yet been updated to > use expat? Yes, the test client is still "old code". I'll fix it as soon as I get the transport working fully again. Can you feel it? We're getting REAL close now!!! :) Jer From owner-jdev@jabber.org Tue Mar 23 13:03:32 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id NAA10884 for jdev-list; Tue, 23 Mar 1999 13:03:32 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from homer.communities.com (homer.communities.com [205.162.51.9]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id NAA10881 for ; Tue, 23 Mar 1999 13:03:29 -0600 Received: from [205.162.51.192] (carlsmack.communities.com [205.162.51.192]) by homer.communities.com (8.9.1/8.9.1) with ESMTP id LAA07338 for ; Tue, 23 Mar 1999 11:05:25 -0800 Message-Id: <199903231905.LAA07338@homer.communities.com> X-Mailer: Microsoft Outlook Express for Macintosh - 4.0a (190) Date: Tue, 23 Mar 1999 11:06:00 -0800 Subject: [JDEV] A question regarding scaling From: "Carl MacDonald" To: jdev@jabber.org Mime-version: 1.0 X-Priority: 3 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: 7bit Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I'm just wondering. Is the plan still to require the user to know what server another user is on to address them? (i.e. name@server) If so, I can think of a number of drawbacks to this, especially when it comes to scaling and wanting to be able to have a user connect to any server transparently for load balancing. Sorry if I'm being obtuse here, but I need to ask these questions as I'm evaluating including support for Jabber in our product. -- Carl From owner-jdev@jabber.org Tue Mar 23 14:12:25 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id OAA11266 for jdev-list; Tue, 23 Mar 1999 14:12:25 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id OAA11263 for ; Tue, 23 Mar 1999 14:12:20 -0600 Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id PAA17516 for ; Tue, 23 Mar 1999 15:11:49 -0500 (EST) Received: from tarot.nhl02.us.ups.com ([10.94.34.20]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id PAA10667 for ; Tue, 23 Mar 1999 15:11:44 -0500 (EST) From: "Thomas Charron" To: Subject: RE: [JDEV] A question regarding scaling Date: Tue, 23 Mar 1999 15:34:38 -0500 Message-ID: <000001be756c$926409e0$14225e0a@tarot.nhl02.us.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 In-Reply-To: <199903231905.LAA07338@homer.communities.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Well, here is how I envision this being able to happen.. Let's say I am twolf@jabber.org. jabber.org contains my password and personal information. I then use my client to attach to jabber.tiac.net, as twolf@jabber.org. jabber.tiac.net would contact jabber.org to validate my password, and tell the server that twolf@jabber.org is connected on jabber.tiac.net, and to forward messages there. This seems to be the best way to deal with this. That way, I'm actually registered on one server, but I can connect to anythat are part of the same network. This is where server<->server messages wouldcome into play, that are listed as 'Work In Progress' on the protocol page. Another option would be to have the transport contact another server and send it as a transport<->server message, but I think it would be better personally to have the servers themselves contact each other. Comments? -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" > -----Original Message----- > From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of > Carl MacDonald > Sent: Tuesday, March 23, 1999 2:06 PM > To: jdev@jabber.org > Subject: [JDEV] A question regarding scaling > > > I'm just wondering. Is the plan still to require the user to know what > server another user is on to address them? (i.e. name@server) > > If so, I can think of a number of drawbacks to this, especially when it > comes to scaling and wanting to be able to have a user connect to > any server > transparently for load balancing. > > Sorry if I'm being obtuse here, but I need to ask these questions as I'm > evaluating including support for Jabber in our product. > > -- > Carl > From owner-jdev@jabber.org Tue Mar 23 15:26:10 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id PAA11765 for jdev-list; Tue, 23 Mar 1999 15:26:10 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from ins3.netins.net (root@ins3.netins.net [167.142.225.3]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id PAA11762 for ; Tue, 23 Mar 1999 15:26:08 -0600 Received: from worf.netins.net (jeremie@worf.netins.net [167.142.225.4]) by ins3.netins.net (8.8.7/8.8.7) with SMTP id PAA02083 for ; Tue, 23 Mar 1999 15:26:07 -0600 Date: Tue, 23 Mar 1999 15:26:06 -0600 (CST) From: Jeremie Miller To: jdev@jabber.org Subject: RE: [JDEV] A question regarding scaling In-Reply-To: <000001be756c$926409e0$14225e0a@tarot.nhl02.us.ups.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > Well, here is how I envision this being able to happen.. Let's say I am > twolf@jabber.org. jabber.org contains my password and personal information. > I then use my client to attach to jabber.tiac.net, as twolf@jabber.org. > jabber.tiac.net would contact jabber.org to validate my password, and tell > the server that twolf@jabber.org is connected on jabber.tiac.net, and to > forward messages there. There are a few issues here... First, having "roaming" setup where the server your connected to talking to your real server doesn't offer any benifits, since everything will end up going back to your real server anyway. I think the direct client->server connection is always going to be the best route, just like how HTTP works. Next: load balancing and lots of simultaneous connections to servers. There are two solutions that I can think of easily. First, do it just like how you'd do a large web site, round-robin DNS or the like. Have a farm of front end servers and a hefty back end database server, and however the DNS resolves is the server you are connected to. This would require the authoring of a special module on the server to do everything through the database, but much of that framework will probably already be in place for other purposes. Secondly, there is a special type of "client" that the server understands, that's a "MULTI" client. It can harbor multiple simultaneous user logins over one connection to the server. A simple proxy could be built that groups of users connect to and everything feeds back to the one main server. I'm quite sure that any needed load balancing or roaming problems can be solved as they are found, the architecture is quite scalable. > > Sorry if I'm being obtuse here, but I need to ask these questions as I'm > > evaluating including support for Jabber in our product. No problem, please ask away :) I get quite a few personal inquiries from others evaluating supporting Jabber and am willing to help in any way I can. Jer From owner-jdev@jabber.org Tue Mar 23 16:21:53 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id QAA11958 for jdev-list; Tue, 23 Mar 1999 16:21:53 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id QAA11955 for ; Tue, 23 Mar 1999 16:21:50 -0600 Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id RAA14621 for ; Tue, 23 Mar 1999 17:21:16 -0500 (EST) Received: from tarot.nhl02.us.ups.com ([10.94.34.20]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id RAA01639 for ; Tue, 23 Mar 1999 17:21:15 -0500 (EST) From: "Thomas Charron" To: Subject: RE: [JDEV] A question regarding scaling Date: Tue, 23 Mar 1999 17:44:09 -0500 Message-ID: <000001be757e$aaadd280$14225e0a@tarot.nhl02.us.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 In-reply-to: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Here's the reasoning I was thinking of wanting to connect to other servers beside's your home server. Different transports that not all servers may run.. Let's use an example of a mod_perl module, or some other HTTP based transport.. If my server doesn't run it, I'd want to be able to connect to ANOTHER server. My case would be while I'm at work behind an HTTP firewall. In this way, if you wish to utilize another transport, you can.. I know this really won't help load balancing in and of itself, I was more stuck on the 'connect to any server' part.. ;-P Although, it would seem to me that 3 server connections that are remotely connected serving several hundred users each would help load balance a little, but not all THAT much.. ;-P Wow, I just had a though about this.. If we did have what I mentioned, you could actually have the 'publically available server' be a different server then the one that actually validating logins, allowing for the authentication to be based on a machine inside a firewall, while the public server is out in the open, but contains none of the password and user data.. Simular to this: ClientA ClientB ClientC \ | / \ | / \ | / \ | / \ | / \ | / \ | / |-----------| |Public | |Server | \-----------/ | | ================|=============== ==== Firewall ==|=============== ================|=============== | /----------------\ | Authentication | | Server | \----------------/ This way an ISP could have their authentication based on the same system that authenticates it's users (Which, if they're bright, is behind some sort of firewall).. -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" > -----Original Message----- > From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of > Jeremie Miller > Sent: Tuesday, March 23, 1999 4:26 PM > To: jdev@jabber.org > Subject: RE: [JDEV] A question regarding scaling > > > > > Well, here is how I envision this being able to happen.. > Let's say I am > > twolf@jabber.org. jabber.org contains my password and personal > information. > > I then use my client to attach to jabber.tiac.net, as twolf@jabber.org. > > jabber.tiac.net would contact jabber.org to validate my > password, and tell > > the server that twolf@jabber.org is connected on jabber.tiac.net, and to > > forward messages there. > > There are a few issues here... > > First, having "roaming" setup where the server your connected to talking > to your real server doesn't offer any benifits, since everything will end > up going back to your real server anyway. I think the direct > client->server connection is always going to be the best route, just like > how HTTP works. > > Next: load balancing and lots of simultaneous connections to servers. > There are two solutions that I can think of easily. First, do it just > like how you'd do a large web site, round-robin DNS or the like. Have a > farm of front end servers and a hefty back end database server, and > however the DNS resolves is the server you are connected to. This would > require the authoring of a special module on the server to do everything > through the database, but much of that framework will probably already be > in place for other purposes. Secondly, there is a special type of > "client" that the server understands, that's a "MULTI" client. It can > harbor multiple simultaneous user logins over one connection to the > server. A simple proxy could be built that groups of users connect to and > everything feeds back to the one main server. > > I'm quite sure that any needed load balancing or roaming problems can be > solved as they are found, the architecture is quite scalable. > > > > Sorry if I'm being obtuse here, but I need to ask these > questions as I'm > > > evaluating including support for Jabber in our product. > > No problem, please ask away :) I get quite a few personal inquiries from > others evaluating supporting Jabber and am willing to help in any way I > can. > > Jer > From owner-jdev@jabber.org Wed Mar 24 15:43:59 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id PAA18430 for jdev-list; Wed, 24 Mar 1999 15:43:59 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id PAA18427 for ; Wed, 24 Mar 1999 15:43:55 -0600 Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id QAA20796 for ; Wed, 24 Mar 1999 16:42:57 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id QAA09437 for ; Wed, 24 Mar 1999 16:42:46 -0500 (EST) From: "Thomas Charron" To: "Jabber Development" Subject: [JDEV] jabber.transport dropping connection.. Date: Wed, 24 Mar 1999 17:05:41 -0500 Message-ID: <000501be7642$75230120$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I noticed that when an XML processing error occurs, jabber.transport promptly drops connection.. I'm wondering if this is how it should be handled, versus perhaps creating a new entry in our little protocol scheme. Parse There was an error parsing your XML Fatal This would also allow for other errors that need to be passed back to the client to be, such as user login errors: Authentication Invalid User ID/Password Mild Comments? Suggestions? -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" From owner-jdev@jabber.org Thu Mar 25 08:30:47 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id IAA21832 for jdev-list; Thu, 25 Mar 1999 08:30:47 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from localhost (jeremie@localhost) by mondo.eppg.com (8.8.7/8.8.7) with SMTP id IAA21829 for ; Thu, 25 Mar 1999 08:30:45 -0600 Date: Thu, 25 Mar 1999 08:30:45 -0600 (EST) From: Jeremie X-Sender: jeremie@mondo.eppg.com To: jdev@jabber.org Subject: RE: [JDEV] A question regarding scaling In-Reply-To: <000001be757e$aaadd280$14225e0a@tarot.nhl02.us.ups.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > Here's the reasoning I was thinking of wanting to connect to other servers > beside's your home server. Different transports that not all servers may > run.. Let's use an example of a mod_perl module, or some other HTTP based > transport.. If my server doesn't run it, I'd want to be able to connect to > ANOTHER server. My case would be while I'm at work behind an HTTP firewall. > In this way, if you wish to utilize another transport, you can.. Absolutely! Fortunately, this is already built into the architecture :) If *your* server doesn't offer a particular transport/feature that you'd like to make use of, all you have to do is find a public one. All transports can optionally have public IP addresses to access them. So say you weren't running the @ICQ transport locally, but xyz.com was and allowed the public to use their installation. They configured the ICQ transport to be icq.jabber.xyz.com, so you just use @icq.jabber.xyz.com. Everything is configurable as to how this works, but all the posibilities are already there. > > Wow, I just had a though about this.. If we did have what I mentioned, you > could actually have the 'publically available server' be a different server > then the one that actually validating logins, allowing for the > authentication to be based on a machine inside a firewall, while the public > server is out in the open, but contains none of the password and user data.. > Simular to this: > > ClientA ClientB ClientC > \ | / > \ | / > \ | / > \ | / > \ | / > \ | / > \ | / > |-----------| > |Public | > |Server | > \-----------/ > | > | > ================|=============== > ==== Firewall ==|=============== > ================|=============== > | > /----------------\ > | Authentication | > | Server | > \----------------/ > > This way an ISP could have their authentication based on the same system > that authenticates it's users (Which, if they're bright, is behind some sort > of firewall).. This is also an excellent idea. How I'd see this working easily would be a special authentication module for the Public Server above, and that module contacts the backend authentication system. This is all very very doable. Jer From owner-jdev@jabber.org Thu Mar 25 08:58:41 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id IAA22050 for jdev-list; Thu, 25 Mar 1999 08:58:41 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from localhost (jeremie@localhost) by mondo.eppg.com (8.8.7/8.8.7) with SMTP id IAA22047 for ; Thu, 25 Mar 1999 08:58:39 -0600 Date: Thu, 25 Mar 1999 08:58:39 -0600 (EST) From: Jeremie X-Sender: jeremie@mondo.eppg.com To: Jabber Development Subject: Re: [JDEV] Error messages (was: jabber.transport dropping connection..) In-Reply-To: <000501be7642$75230120$62205e0a@tarot.telecom.ups.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > I noticed that when an XML processing error occurs, jabber.transport > promptly drops connection.. I'm wondering if this is how it should be > handled, versus perhaps creating a new entry in our little protocol scheme. > > > Parse > There was an error parsing your XML > Fatal > > > This would also allow for other errors that need to be passed back to the > client to be, such as user login errors: > > > Authentication > Invalid User ID/Password > Mild > > > Comments? Suggestions? Right now the approach is to actually send a with error. I've gone back and forth with myself about this a few times, and am really sitting on the fence. On one hand, I like having errors be special messages that clients can *optionally* intercept, or just deliver them. This is just one less thing that a client would be _required_ to deal with and one less, and one less thing the server and transports have to handle. Basically, if you consider "messages" to be your primary communication channel(like email) then errors would just be delivered via that channel. On the other hand, it's really tempting to add to the protocol and create a nice clean way of communicating errors. I think I'm still of the attitude that if we can utilize the existing protocol to do this *and* add the feature of allowing clients to be simplier if they want to be, than using messages to communicate errors is better. It's difficult to strike a good balance between protocol bloat and overloading the existing structure. Currently, I see things breaking down thusly: One time value communications: Background "status" communications: Client only sesion communications: Global static information communications (this is new) Errors definately fall into the first category :) On the first subject, just disconnecting when XML errors happen: yes, it's probably not the nicest thing to do... It shouldn't happen in the "real world" often, but I'll have it at least send an error of some type before it disconnects. Jer From owner-jdev@jabber.org Thu Mar 25 12:19:07 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id MAA22974 for jdev-list; Thu, 25 Mar 1999 12:19:07 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id MAA22971 for ; Thu, 25 Mar 1999 12:19:04 -0600 Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id NAA18053 for ; Thu, 25 Mar 1999 13:18:29 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id NAA02351 for ; Thu, 25 Mar 1999 13:18:28 -0500 (EST) From: "Thomas Charron" To: Subject: RE: [JDEV] Error messages (was: jabber.transport dropping connection..) Date: Thu, 25 Mar 1999 13:41:24 -0500 Message-ID: <002901be76ef$15de3ce0$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal In-reply-to: Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > Right now the approach is to actually send a with > error. I've gone back and forth with myself about this a few > times, and am really sitting on the fence. Actually, is the context still valid using expat? Aka, would this: jeremie Your password did NOT match your user ID FailedValidation still be valid? It IS valid XML, but I wasn't absolutly sure HOW 100% expat IS. Looks to me like it can. This way we can easily usethe message tag for all messages going to/from clients, but still be able to specify a message 'type'. If no type is specified, we assume it's a normal message. Clients who do not intercept errors would merely pass this along as a message, but it would give the clients the ability to optionally catch different message 'types' themselves.. > On one hand, I like having errors be special messages that clients can > *optionally* intercept, or just deliver them. This is just one less thing > that a client would be _required_ to deal with and one less, and one less > thing the server and transports have to handle. Basically, if you > consider "messages" to be your primary communication channel(like email) > then errors would just be delivered via that channel. See above.. ;-P I think it addresses it, and allows for both.. > On the other hand, it's really tempting to add to the protocol and create > a nice clean way of communicating errors. Which is why we predefine a list 'message types' that are recomended to be supported within clients, such as 'error'. Nice, clean, and requires no additional changes to the protocol.. > I think I'm still of the attitude that if we can utilize the existing > protocol to do this *and* add the feature of allowing clients to be > simplier if they want to be, than using messages to communicate errors is > better. Done.. Next!! Number 93.. Number 93.. (As in, take a number from the pretty red number giver outer..) -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" From owner-jdev@jabber.org Thu Mar 25 14:36:26 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id OAA23667 for jdev-list; Thu, 25 Mar 1999 14:36:26 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from ins8.netins.net (ins8.netins.net [167.142.225.8]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id OAA23664 for ; Thu, 25 Mar 1999 14:36:23 -0600 Received: from worf.netins.net (jeremie@worf.netins.net [167.142.225.4]) by ins8.netins.net (8.8.7/8.8.7) with SMTP id OAA28013 for ; Thu, 25 Mar 1999 14:36:18 -0600 (CST) Date: Thu, 25 Mar 1999 14:36:18 -0600 (CST) From: Jeremie Miller To: jdev@jabber.org Subject: RE: [JDEV] Error messages (was: jabber.transport dropping connection..) In-Reply-To: <002901be76ef$15de3ce0$62205e0a@tarot.telecom.ups.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > > Actually, is the context still valid using > expat? Aka, would this: > > > jeremie > Your password did NOT match your user ID > FailedValidation > > > still be valid? It IS valid XML, but I wasn't absolutly sure HOW 100% > expat IS. Looks to me like it can. This way we can easily usethe message > tag for all messages going to/from clients, but still be able to specify a > message 'type'. If no type is specified, we assume it's a normal message. > Clients who do not intercept errors would merely pass this along as a > message, but it would give the clients the ability to optionally catch > different message 'types' themselves.. Yes, it is absolutely valid, and expat 100% a conforming well-formed XML parser. Offhand, it looks good, and I like it... it "fits the bill" quite nicely. I'll play around tonight with the sources and if I don't hit a brick wall, I'll just add this in. That means that there will probably be a few predefined types that the server supports/uses, and a range of ErrorType types. But, if a client doesn't support it, it will pass through to the user nicely. It also opens up future expandability, such as type='filesend' or type='chainvite' that clients can optionally support. Excellent idea, thanks! Jer From owner-jdev@jabber.org Fri Mar 26 15:35:52 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id PAA29328 for jdev-list; Fri, 26 Mar 1999 15:35:52 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from localhost (jeremie@localhost) by mondo.eppg.com (8.8.7/8.8.7) with SMTP id PAA29325 for ; Fri, 26 Mar 1999 15:35:49 -0600 Date: Fri, 26 Mar 1999 15:35:49 -0600 (EST) From: Jeremie X-Sender: jeremie@mondo.eppg.com To: jdev@jabber.org Subject: [JDEV] jabber.org updated Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org http://jabber.org/ I just updated a few pages and restructured some other areas of the site. Feel free to take a peak and let me know if there are any glaring problems, spelin mistakes, broken links, etc... Warning: there are quite a few empty pages that I'll be filling in with documentation yet, RSN! DR 0.6 with the new protocol will be out either before the end of March or in very early April, joy! Thanks, Jer From owner-jdev@jabber.org Fri Mar 26 16:52:00 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id QAA29598 for jdev-list; Fri, 26 Mar 1999 16:52:00 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id QAA29595 for ; Fri, 26 Mar 1999 16:51:55 -0600 Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id RAA18134 for ; Fri, 26 Mar 1999 17:51:23 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id RAA17127 for ; Fri, 26 Mar 1999 17:51:23 -0500 (EST) From: "Thomas Charron" To: Subject: [JDEV] Win client, File Transfers, invite tag.. Date: Fri, 26 Mar 1999 18:14:27 -0500 Message-ID: <001a01be77de$6530e1e0$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I will promise to at least have a Windows test client ready by then. I've been unfortionatly busy as heck, and haven't had any time to have a working client with the new protocol complete. Looks for a big Win32 checkin to the source tree sometime early next week. I'm also disecting using the same expat sources you are using for parsing the XML, making it a bit easier to look at the client. I've also figured out a way to tentativly do file transfers via messages.. What I've worked out is to have the client UUENCODE the file, then send it in chunks of message tags, like this: TwOlf 82646 somefile.txt 100 10 1074 HJFGSHGFSGFHGY67835627T4HGDY5 Here is a brief rundown of how I'm looking at doing it, and what the tags mean: Used this to pass thru as a message, but a type of wintranfer. Used wintransfer so it does not interfere with anything anyone else is working on, aka, I'm fine as long as no one else uses this type. TwOlf Obviouse.. Who this packet is going to. Storing all of my data in the ext tag.. Good question here, though.. It it acceptable to have additional XML tags within the ext tag? 82646 A Randomly generated number to 'identify' this transfer somefile.txt Filename being transfered.. (May be saved differently, but this is what it WAS called) 100 Total packets in this transfer.. Basically, I uuencode the file and split the resulting set into X number of chunks, each being a certain size (What do you think would be optimal for the servers to handle correctly? I'm assuming something smaller, so 10 transfers don't result in one server bogging memory wise) 10 Current packet number.. This instance is packet #10 of 100 total. 1074 The total size of the uuencoded data. Used to validate that it came thru OK.. HJFGSHGFSGFHGY67835627T4HGDY5 The uuencoded data. Will all this be acceptable via the servers? I BELIEVE so, but I'm stilllooking thru the transport and jabberbox source to ensure so.. I'm also considering adding a 'response' packet, so 100 packets aren't sent, the user get's 50, signs off,and the person who sent them get's 50 'rejected' messages becouse they couldn;t be delivered, but that would require using additional bandwidth. The other neat idea would be to be able to send messages as above to offline users, which would, in turn, be stored offline, and would allow file transfers tooffline users, as the's would still be stored on the server, but it would require turning 'off' the need for a response for each packet, which is OK, but it'd mean you'd need some sort of tag in ext to tell the server NOT to send a 'This user is offline' message. Also, I've noticed the 'invite' that is checked in . Should this now be moved to instead of having jabber.transport check the tag for invite? Ideas? Comments? People who want me to STOP asking questions and just shut the heck up? ;-P -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" > -----Original Message----- > From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of > Jeremie > Sent: Friday, March 26, 1999 4:36 PM > To: jdev@jabber.org > Subject: [JDEV] jabber.org updated > > > http://jabber.org/ > > I just updated a few pages and restructured some other areas of the site. > Feel free to take a peak and let me know if there are any glaring > problems, spelin mistakes, broken links, etc... > > Warning: there are quite a few empty pages that I'll be filling in with > documentation yet, RSN! > > DR 0.6 with the new protocol will be out either before the end of March or > in very early April, joy! > > Thanks, > > Jer > From owner-jdev@jabber.org Fri Mar 26 17:17:05 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id RAA29755 for jdev-list; Fri, 26 Mar 1999 17:17:05 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from gulf.csc.UVic.CA (gulf.csc.UVic.CA [142.104.105.200]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id RAA29752 for ; Fri, 26 Mar 1999 17:17:03 -0600 From: qbradley@csc.UVic.CA Received: from thetis.csc.UVic.CA (thetis.csc.UVic.CA [142.104.105.204]) by gulf.csc.UVic.CA (8.8.8/8.8.8) with SMTP id PAA21108 for ; Fri, 26 Mar 1999 15:17:01 -0800 (PST) Received: from localhost by thetis.csc.UVic.CA (SMI-8.6/SMI-SVR4) id PAA21169; Fri, 26 Mar 1999 15:16:59 -0800 Date: Fri, 26 Mar 1999 15:16:58 -0800 (PST) X-Sender: qbradley@thetis To: jdev@jabber.org Subject: Re: [JDEV] Win client, File Transfers, invite tag.. In-Reply-To: <001a01be77de$6530e1e0$62205e0a@tarot.telecom.ups.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I think this is a great idea, but I have a few suggestions. Why don't you call it "uumessagetransfer" instead of "wintransfer", as that would be a more accurate description of what it does. Also, instead of using a random number to idenfity file transfers, maybe an md5 hash of the original file would be better. One thing to consider is how it handles sending enormous files. It would be desireable that a file transfer could be started without reading in the entire file in advance, or converting it to uuencoded format in advance. Is it possible to precisely predict the uuencoded size from the original size? If not, then perhaps using the original files size instead of the uuencoded files size in the protocol would allow the file to be uuencoded bit by bit while it was transfered. As for packet sizes, larger packets might actually be better than smaller packets, but of course there will be some middle point that works out the best. The reason I think this might be the case is that smaller packets will require more processing by the server. Processing time is probably more valuable than memory. Also, memory might not be saved at all by smaller packets because you would probably just end up sending more in a given period of time. This would mean more processing on the server, as well as more memory use because of the increased overhead from the information with each packet. In fact, a packet size of 60k or so might be better. Many files could be sent in one packet, which would make it quite efficient. This brings up another question, how fast to send packets? If they are sent as fast as possible, they could pile up at the server, which wouldn't be nice for the server. But if you have replies being sent, you could time them to get an idea of how fast things are going through and pace the rate at which you send them. But this adds complication. Mabye replies and pacing should be an optional feature for advanced implemenations. Just some thoughts, Quetzalcoatl Bradley qbradley@csc.uvic.ca From owner-jdev@jabber.org Fri Mar 26 17:22:40 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id RAA29782 for jdev-list; Fri, 26 Mar 1999 17:22:40 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from gulf.csc.UVic.CA (gulf.csc.UVic.CA [142.104.105.200]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id RAA29779 for ; Fri, 26 Mar 1999 17:22:37 -0600 From: qbradley@csc.UVic.CA Received: from thetis.csc.UVic.CA (thetis.csc.UVic.CA [142.104.105.204]) by gulf.csc.UVic.CA (8.8.8/8.8.8) with SMTP id PAA22605 for ; Fri, 26 Mar 1999 15:22:36 -0800 (PST) Received: from localhost by thetis.csc.UVic.CA (SMI-8.6/SMI-SVR4) id PAA21219; Fri, 26 Mar 1999 15:22:34 -0800 Date: Fri, 26 Mar 1999 15:22:33 -0800 (PST) X-Sender: qbradley@thetis To: jdev@jabber.org Subject: [JDEV] Protocl proposal "priority bit" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Thomas Charron's idea about sending files as Jabber messages has given me an idea that might be useful generally. Perhaps there should be an attribute or tag that acts like a priority bit, like in ATM packets. High priority packets would behave as already described. Low priority packets would behave differently in one circumstance. If a low priority packet gets to its destination server, and finds the user in question is not logged in, the packet is thrown away. This would be great for "file transfer" packets.. maybe 50 of them have already been sent when a user disconnects. It is probably not desireable for them all to hang around on the server until the user reconnections. Instead the transfer should be resumed later. There is another use of the packet. Messages which are time limited. Perhaps I send a message to my coworker "We are leaving for lunch right now". I don't want him to get it an hour later. Either they should get it right away or not at all. Whether anyone would ever make use of such a feature or not depends on how easy it was, a user interface issue. Anyway, ramble ramble... anyone else think it is an idea with merit? Quetzalcoatl Bradley qbradley@csc.uvic.ca From owner-jdev@jabber.org Fri Mar 26 19:39:22 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id TAA30355 for jdev-list; Fri, 26 Mar 1999 19:39:22 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id TAA30352 for ; Fri, 26 Mar 1999 19:39:18 -0600 Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id UAA29933 for ; Fri, 26 Mar 1999 20:38:46 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id UAA08350 for ; Fri, 26 Mar 1999 20:38:46 -0500 (EST) From: "Thomas Charron" To: Subject: RE: [JDEV] Win client, File Transfers, invite tag.. Date: Fri, 26 Mar 1999 21:01:56 -0500 Message-ID: <000101be77f5$cae43980$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of > qbradley@csc.UVic.CA > Subject: Re: [JDEV] Win client, File Transfers, invite tag.. > I think this is a great idea, but I have a few suggestions. Why don't you > call it "uumessagetransfer" instead of "wintransfer", as that would be a > more accurate description of what it does. Ordinarily, yes, I would use something like that. But do to the current status of client development, I figured something that I KNEW I could use that would identify it without messing with something else someone else may be developing was much more prudent.. > Also, instead of using a random number to idenfity file transfers, maybe > an md5 hash of the original file would be better. Either way would work, but a random number is easier.. ;-P > One thing to consider is how it handles sending enormous files. It would > be desireable that a file transfer could be started without reading in the > entire file in advance, or converting it to uuencoded format in advance. > Is it possible to precisely predict the uuencoded size from the original > size? If not, then perhaps using the original files size instead of the > uuencoded files size in the protocol would allow the file to be uuencoded > bit by bit while it was transfered. Yes, this would be the best.. This was merely done as a quick 'I can develop file transfer REALLY easy with this'. And it also a VERY reliable way to transfer binary data via a text transfer.. Also, the exact file size is used to tell if it all worked.. Again, merely a quickie to do it.. > As for packet sizes, larger packets might actually be better than smaller > packets, but of course there will be some middle point that works out the > best. It's a toss up between proccesser time and memory performance.. Smaller packets leadto less memory usage, but more 'packets'. Getting to small would be silly, but I was figuring 10-50 k at a chunk.. > The reason I think this might be the case is that smaller packets will > require more processing by the server. Processing time is probably more > valuable than memory. Also, memory might not be saved at all by smaller > packets because you would probably just end up sending more in a given > period of time. This would mean more processing on the server, as well as > more memory use because of the increased overhead from the information > with each packet. I would say for future reference, I'd let the server at some point give a 'prefered packet size'. This would allow the transport to give that particular data itself.. But as I said, this is a quickie, so it'll prob. all change.. > In fact, a packet size of 60k or so might be better. Many files could be > sent in one packet, which would make it quite efficient. See above.. Currently, my sceme (from a client side) doesn;t allow more then one file per send (But multiple sends at a a TIME are ok). Again, scratch it off to a quickie.. > This brings up another question, how fast to send packets? If they are > sent as fast as possible, they could pile up at the server, which wouldn't > be nice for the server. But if you have replies being sent, you could > time them to get an idea of how fast things are going through and pace the > rate at which you send them. But this adds complication. Exactly why I had the idea of replies, but that also get's in the way. I'm figuring ONE message sent that the user is offline, then a question as to if you want to send it as an offline message, not using the 'client-server' sceme.. > Mabye replies and pacing should be an optional feature for advanced > implemenations. See my last reply.. ;-P -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" From owner-jdev@jabber.org Fri Mar 26 20:29:31 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id UAA30568 for jdev-list; Fri, 26 Mar 1999 20:29:31 -0600 Received: from ziggy.jeremie.com (jer@cscd-02-30.dialup.netins.net [209.152.71.159]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id UAA30565 for ; Fri, 26 Mar 1999 20:29:27 -0600 Received: from localhost (jer@localhost) by ziggy.jeremie.com (8.8.7/8.8.7) with ESMTP id UAA13212 for ; Fri, 26 Mar 1999 20:32:25 -0600 X-Authentication-Warning: ziggy.jeremie.com: jer owned process doing -bs Date: Fri, 26 Mar 1999 20:32:24 -0600 (EST) From: Jeremie To: jdev@jabber.org Subject: Re: [JDEV] Win client, File Transfers, invite tag.. In-Reply-To: <001a01be77de$6530e1e0$62205e0a@tarot.telecom.ups.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > I will promise to at least have a Windows test client ready by then. I've > been unfortionatly busy as heck, and haven't had any time to have a working > client with the new protocol complete. Looks for a big Win32 checkin to the > source tree sometime early next week. I'm also disecting using the same > expat sources you are using for parsing the XML, making it a bit easier to > look at the client. Excellent on all of the above points! The C in /lib/* should be mostly XP, so you might want to look at just using the whole common lib... but there might be some excellent reasons not to for win32 stuff. Realistically, any XML parser should do... just use whatever is most convenient. > I've also figured out a way to tentativly do file transfers via messages.. > What I've worked out is to have the client UUENCODE the file, then send it > in chunks of message tags, like this: > > [large discussion snip'd] I should have spoken up earlier on file transfers :) I'll try to write up something more concrete soon here, but here is where I've been heading with file transfers: HTTP/1.1 Yup, that's right... let's use HTTP/1.1! It already has EVERYTHING needed to handle any type of file transfer, and it's commonplace, and it works. Here's how, simple version: user x sending file to user z x selects file to send x starts small HTTP/1.1 file on high port for THAT FILE ONLY x sends z a special message(abbreviated): http://123.231.12.21:23456/filename.zip z recieves message and uses HTTP/1.1 to GET file Ok, benifits: HTTP/1.1 can do resumes if it get's broken. ICQ/AIM transports could impliment "translator" daemons for it Recieving client could just spawn browser to fetch file Happens in background, leaves Jabber connection to work normally This could be simply a URL message, not specific for files I could go on and on, but I'm outta time :( Further: A special module could be written on the Jabber server to use this functionaliy for a "file archive". The client would send a jabber message to the module and ask for a repository, this would be configurable obviously so only special users could use it or have size limits. The module would reply with an: http://serverIPaddress:port/. The client would then PUT files up there via HTTP, and authenticate them with the users username/password. Then it would send out the location to GET them like any other file message as above. This would allow you to send files to offline users, as well as send files to groups of users, just upload it once and they all download it. It is also a solution for transferring files if you are going through a firewall. Actually, it could end up just being a normal apache and a special module or similiar... and you'd have your own personal webspace... There are some issues here yet, but I think this is the best way to go in some form. I've really gotta sit down and think this through clearly and get it written down, but hopefully this will get the discussion started :) > > Also, I've noticed the 'invite' that is checked in . Should this now > be moved to instead of having jabber.transport check > the tag for invite? Yup, just didn't get a chance to do that yet... > Ideas? Comments? People who want me to STOP asking questions and just > shut the heck up? ;-P Ask away, discussion is good! Jer From owner-jdev@jabber.org Fri Mar 26 20:31:40 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id UAA30590 for jdev-list; Fri, 26 Mar 1999 20:31:40 -0600 Received: from ziggy.jeremie.com (jer@cscd-02-30.dialup.netins.net [209.152.71.159]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id UAA30586 for ; Fri, 26 Mar 1999 20:31:37 -0600 Received: from localhost (jer@localhost) by ziggy.jeremie.com (8.8.7/8.8.7) with ESMTP id UAA13217 for ; Fri, 26 Mar 1999 20:34:36 -0600 X-Authentication-Warning: ziggy.jeremie.com: jer owned process doing -bs Date: Fri, 26 Mar 1999 20:34:36 -0600 (EST) From: Jeremie To: jdev@jabber.org Subject: Re: [JDEV] Win client, File Transfers, invite tag.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > > This brings up another question, how fast to send packets? If they are > sent as fast as possible, they could pile up at the server, which wouldn't > be nice for the server. But if you have replies being sent, you could > time them to get an idea of how fast things are going through and pace the > rate at which you send them. But this adds complication. As it is right now, with the way TCP/IP stacks work, much of the data will be buffered until the server can deal with it or the client will wait until the server catches up. > Mabye replies and pacing should be an optional feature for advanced > implemenations. Yes, definately... threading on the server side will also help keep it up to speed. Jer From owner-jdev@jabber.org Fri Mar 26 20:36:28 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id UAA30646 for jdev-list; Fri, 26 Mar 1999 20:36:28 -0600 Received: from ziggy.jeremie.com (jer@cscd-02-30.dialup.netins.net [209.152.71.159]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id UAA30643 for ; Fri, 26 Mar 1999 20:36:24 -0600 Received: from localhost (jer@localhost) by ziggy.jeremie.com (8.8.7/8.8.7) with ESMTP id UAA13222 for ; Fri, 26 Mar 1999 20:39:23 -0600 X-Authentication-Warning: ziggy.jeremie.com: jer owned process doing -bs Date: Fri, 26 Mar 1999 20:39:23 -0600 (EST) From: Jeremie To: jdev@jabber.org Subject: Re: [JDEV] Protocl proposal "priority bit" In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org This is definately a possibility(and was originally something SMTP was supposed to do but it never came through). What's cool, is that with the way the Jabber transport/server currently works, this is completly up to the module, so it can be controlled externally to the server. Fun fun! Jer On Fri, 26 Mar 1999 qbradley@csc.UVic.CA wrote: > > Thomas Charron's idea about sending files as Jabber messages has given me > an idea that might be useful generally. > > Perhaps there should be an attribute or tag that acts like a priority bit, > like in ATM packets. High priority packets would behave as already > described. Low priority packets would behave differently in one > circumstance. > > If a low priority packet gets to its destination server, and finds the > user in question is not logged in, the packet is thrown away. > > This would be great for "file transfer" packets.. maybe 50 of them have > already been sent when a user disconnects. It is probably not desireable > for them all to hang around on the server until the user reconnections. > Instead the transfer should be resumed later. > > There is another use of the packet. Messages which are time limited. > Perhaps I send a message to my coworker "We are leaving for lunch right > now". I don't want him to get it an hour later. Either they should get > it right away or not at all. Whether anyone would ever make use of such a > feature or not depends on how easy it was, a user interface issue. > > Anyway, ramble ramble... anyone else think it is an idea with merit? > > Quetzalcoatl Bradley > qbradley@csc.uvic.ca > > From owner-jdev@jabber.org Sat Mar 27 02:06:10 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id CAA31871 for jdev-list; Sat, 27 Mar 1999 02:06:10 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from gulf.csc.UVic.CA (gulf.csc.UVic.CA [142.104.105.200]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id CAA31868 for ; Sat, 27 Mar 1999 02:06:07 -0600 From: qbradley@csc.UVic.CA Received: from thetis.csc.UVic.CA (thetis.csc.UVic.CA [142.104.105.204]) by gulf.csc.UVic.CA (8.8.8/8.8.8) with SMTP id AAA09275 for ; Sat, 27 Mar 1999 00:06:06 -0800 (PST) Received: from localhost by thetis.csc.UVic.CA (SMI-8.6/SMI-SVR4) id AAA27696; Sat, 27 Mar 1999 00:06:03 -0800 Date: Sat, 27 Mar 1999 00:06:03 -0800 (PST) X-Sender: qbradley@thetis To: jdev@jabber.org Subject: Re: [JDEV] Win client, File Transfers, invite tag.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org On Fri, 26 Mar 1999, Jeremie wrote: > As it is right now, with the way TCP/IP stacks work, much of the data will > be buffered until the server can deal with it or the client will wait > until the server catches up. Aha! But we still have trouble! In a typical situation, I have a network connection to a server, and it either has, or makes, network connections to the destination server, which has a connection to the destination user on that server. I start flooding my server with messages as fast as I can, across my cable modem. There is a lot of congestion in between my server and the destination server, so all my packets pile up on my server as it tries to send them to the other server. There are three seperate TCP/IP connections involved, so if the 2nd or 3rd connection is slower than the 1st or 2nd, messages will pile up. In the case of using HTTP/1.1 and a direct connection between clients, this wouldn't be a problem because only one TCP/IP connection is involved. The problem with the scheme you suggested for file transfers, as I understand it, is that you send your IP number to the other user. Disregarding privacy issues, this scheme will fail in at least two situations. One is using a firewall and IP forwarding, or if you are using a proxy (kinda the same situation really I guess). Actually come to think of it would only fail in the case where you were behind a firewall, wouldn't it? Anyway, another advantage of implementing file transfers as uuencoded messages is that it would be a REALLY easy way to implement it in the client. Another solution would be to implement both and see what works out best :-) Quetzalcoatl Bradley qbradley@csc.uvic.ca From owner-jdev@jabber.org Sat Mar 27 03:10:52 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id DAA32094 for jdev-list; Sat, 27 Mar 1999 03:10:52 -0600 Received: from ziggy.jeremie.com (jer@cscd-02-38.dialup.netins.net [209.152.71.167]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id DAA32091 for ; Sat, 27 Mar 1999 03:10:49 -0600 Received: from localhost (jer@localhost) by ziggy.jeremie.com (8.8.7/8.8.7) with ESMTP id DAA13484 for ; Sat, 27 Mar 1999 03:13:53 -0600 X-Authentication-Warning: ziggy.jeremie.com: jer owned process doing -bs Date: Sat, 27 Mar 1999 03:13:53 -0600 (EST) From: Jeremie To: jdev@jabber.org Subject: Re: [JDEV] Win client, File Transfers, invite tag.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > Aha! But we still have trouble! In a typical situation, I have a network > connection to a server, and it either has, or makes, network connections > to the destination server, which has a connection to the destination user > on that server. > > I start flooding my server with messages as fast as I can, across my cable > modem. There is a lot of congestion in between my server and the > destination server, so all my packets pile up on my server as it tries to > send them to the other server. > > There are three seperate TCP/IP connections involved, so if the 2nd or 3rd > connection is slower than the 1st or 2nd, messages will pile up. Yes, they will pile up. They will be buffered in your server and streamed out as bandwidth permits. > The problem with the scheme you suggested for file transfers, as I > understand it, is that you send your IP number to the other user. Yes, but the client<->client HTTP transfer is optional. I'd like to see most of the file transfers happen via a server module/daemon. Either the sender PUT's the file on the server then notifies the recipient, or a special streaming pipe could easily be written so that both clients connect to the server and the data is streamed from one socket to another. The client<->client file transfer would be most useful in certian situations where the two clients are closer than the client->server->client, such as two people on a LAN and the server is on another part of the net. > Disregarding privacy issues, this scheme will fail in at least two > situations. One is using a firewall and IP forwarding, or if you are > using a proxy (kinda the same situation really I guess). Actually come to > think of it would only fail in the case where you were behind a firewall, > wouldn't it? It depends on the firewall... some detect at the protocol level and would typically allow HTTP, some do address translation, and some are locked up tight. Still, if your client can connect to the server, then the way to get around any firewall issues would be to just use the server module to handle the file transfer. > Anyway, another advantage of implementing file transfers as > uuencoded messages is that it would be a REALLY easy way to implement it > in the client. Only partially true... if the client just wanted to support HTTP/1.1 PUTs, it just has to open a socket(which it already has to know how to do) print a few mostly static strings, then dump the file to the socket(or read for a GET). IMHO it seems far simpler than reassembling messages and uudecoding them, which in the process added extra size, download time, and server load. I really want to avoid in any way possible using or encouraging the over-use of the main Jabber protocol for anything other than what it was designed to do, which is communicate micro information(or micromation) instantly. I love these discussions though, forces me to rethink my approaches :) Jer From owner-jdev@jabber.org Sat Mar 27 04:10:45 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id EAA32390 for jdev-list; Sat, 27 Mar 1999 04:10:45 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from smtp.doruk.net.tr (smtp.doruk.net.tr [212.58.4.4]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id EAA32387 for ; Sat, 27 Mar 1999 04:10:40 -0600 Received: from doruk.net.tr (zeus.doruk.net.tr [212.58.4.10]) by smtp.doruk.net.tr (8.8.5/SCO5) with SMTP id MAA07139 for ; Sat, 27 Mar 1999 12:31:33 +0200 (TSI) Received: from l086.pri.ppp.doruk.net.tr by doruk.net.tr (SMI-8.6/SMI-SVR4) id MAA13464; Sat, 27 Mar 1999 12:04:51 +0200 Date: Sat, 27 Mar 1999 12:09:25 +0200 (EET) From: "Kemal 'Disq' Hadimli" X-Sender: disq@heart_of_gold.localdomain To: jdev@jabber.org Subject: Re: [JDEV] Protocl proposal "priority bit" In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Hi. On Fri, 26 Mar 1999 qbradley@csc.UVic.CA wrote: > Anyway, ramble ramble... anyone else think it is an idea with merit? very clever. ;) bye, disqk Microsoft is not the answer. Microsoft is the question. NO (or Linux) is the answer. From owner-jdev@jabber.org Sat Mar 27 04:18:56 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id EAA32451 for jdev-list; Sat, 27 Mar 1999 04:18:56 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from smtp.doruk.net.tr (smtp.doruk.net.tr [212.58.4.4]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id EAA32448 for ; Sat, 27 Mar 1999 04:18:52 -0600 Received: from doruk.net.tr (zeus.doruk.net.tr [212.58.4.10]) by smtp.doruk.net.tr (8.8.5/SCO5) with SMTP id MAA07402 for ; Sat, 27 Mar 1999 12:39:55 +0200 (TSI) Received: from l086.pri.ppp.doruk.net.tr by doruk.net.tr (SMI-8.6/SMI-SVR4) id MAA13675; Sat, 27 Mar 1999 12:13:18 +0200 Date: Sat, 27 Mar 1999 12:17:52 +0200 (EET) From: "Kemal 'Disq' Hadimli" X-Sender: disq@heart_of_gold.localdomain To: jdev@jabber.org Subject: Re: [JDEV] Win client, File Transfers, invite tag.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Hi. On Fri, 26 Mar 1999, Jeremie wrote: > I'll try to write up something more concrete soon here, but here is where > I've been heading with file transfers: > > HTTP/1.1 > > Yup, that's right... let's use HTTP/1.1! It already has EVERYTHING needed > to handle any type of file transfer, and it's commonplace, and it works. this would be the best. and the file repository idea is also good. ;) bye, disqk Microsoft is not the answer. Microsoft is the question. NO (or Linux) is the answer. From owner-jdev@jabber.org Mon Mar 29 13:21:37 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id NAA09968 for jdev-list; Mon, 29 Mar 1999 13:21:37 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id NAA09965 for ; Mon, 29 Mar 1999 13:21:34 -0600 Received: by xavier.ups.com (8.9.1a/8.9.1/UPS) id OAA10039 for jdev@jabber.org; Mon, 29 Mar 1999 14:21:02 -0500 (EST) Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id OAA09958 for ; Mon, 29 Mar 1999 14:20:57 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id OAA23842 for ; Mon, 29 Mar 1999 14:20:54 -0500 (EST) From: "Thomas Charron" To: "Jabber Development" Subject: [JDEV] Concern regarding transport overload.. Date: Mon, 29 Mar 1999 14:43:56 -0500 Message-ID: <000801be7a1c$7ba2eaa0$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I have a bit of a concern that I'd like to point out.. How many 'transports' are we going to have on a basic server. I think that a basic server should be able to support several of the things that we've all said would be best in a module, but I'm concerned about people needing to run 10 DIFFERENT transport programs to supply this functionality. Would it be possible for the basic jabber.transport to be able to provide these abilities without needing to run all of these transports? Now, don't get me wrong, I LIKE being able to throw everything in modules. What I'm concerned about is the one or two executable ISP installs that have been mentioned.. Any ideas on how we can have the best of both worlds? Is it possible to have TWO different transports, an 'easy to use' install that provides most of the basic services in one executable, and more advanced that uses seperate transports for each service? The easy to use interface could actually be achived if someone made all of the transports thread safe, and compile them all together in one executable, using a macro to replace the main function with something else, and call them all running in their own thread. This would be reliant on someone here knowing threading on a *nix box, which, unfortionatly, I do not, so I'm of little help there. -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" From owner-jdev@jabber.org Mon Mar 29 13:29:17 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id NAA10038 for jdev-list; Mon, 29 Mar 1999 13:29:17 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id NAA10035 for ; Mon, 29 Mar 1999 13:29:14 -0600 Received: by xavier.ups.com (8.9.1a/8.9.1/UPS) id OAA15636 for jdev@jabber.org; Mon, 29 Mar 1999 14:28:35 -0500 (EST) Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id OAA15391 for ; Mon, 29 Mar 1999 14:28:17 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id OAA28527 for ; Mon, 29 Mar 1999 14:28:07 -0500 (EST) From: "Thomas Charron" To: Subject: RE: [JDEV] Win client, File Transfers, invite tag.. Date: Mon, 29 Mar 1999 14:51:09 -0500 Message-ID: <000a01be7a1d$7d9c7b40$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: Importance: Normal Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of > qbradley@csc.UVic.CA > Subject: Re: [JDEV] Win client, File Transfers, invite tag.. > The problem with the scheme you suggested for file transfers, as I > understand it, is that you send your IP number to the other user. > Disregarding privacy issues, this scheme will fail in at least two > situations. One is using a firewall and IP forwarding, or if you are > using a proxy (kinda the same situation really I guess). Actually come to > think of it would only fail in the case where you were behind a firewall, Actually, I do something like this all the time thru a firewall.. Most HTTP libs you'd use support going thu a firewall, so as long as you takeinto consideration for this, it's not a problem. > wouldn't it? Anyway, another advantage of implementing file transfers as > uuencoded messages is that it would be a REALLY easy way to implement it > in the client. > Another solution would be to implement both and see what works out best > :-) Well, I actually PREFER the HTTP method, but I am still going to complete the uudecode method as well. The primary reason for this is a forsee this as being a prefered way on encrypted file transition. Using a PGP lib or something to encrypt uuencoded data would be SO easy to implement it just begs for me to finish it to be able to provide it. HTTP transfer COULD provide encryption as well, but I'm not going to provide SSL encryption in a client at this point. Actually, we now se the benifits of the protocol. Both of these CAN be supported as we speak, without ANY changes to the servers and/or transports as they sit now.. I'm getting more and more addicted to the possibilities of XML for communications every day.. -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" From owner-jdev@jabber.org Mon Mar 29 13:37:56 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id NAA10125 for jdev-list; Mon, 29 Mar 1999 13:37:56 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id NAA10121 for ; Mon, 29 Mar 1999 13:37:51 -0600 Received: by xavier.ups.com (8.9.1a/8.9.1/UPS) id OAA21837 for jdev@jabber.org; Mon, 29 Mar 1999 14:37:18 -0500 (EST) Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id OAA21566 for ; Mon, 29 Mar 1999 14:37:01 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id OAA02640 for ; Mon, 29 Mar 1999 14:36:54 -0500 (EST) From: "Thomas Charron" To: Subject: RE: [JDEV] Win client, File Transfers, invite tag.. Date: Mon, 29 Mar 1999 14:59:55 -0500 Message-ID: <000c01be7a1e$b7158140$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: Importance: Normal Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of > Jeremie > Subject: Re: [JDEV] Win client, File Transfers, invite tag.. > > I will promise to at least have a Windows test client ready > by then. I've > > been unfortionatly busy as heck, and haven't had any time to > have a working > > client with the new protocol complete. Looks for a big Win32 > checkin to the > Excellent on all of the above points! The C in /lib/* should be mostly > XP, so you might want to look at just using the whole common lib... but > there might be some excellent reasons not to for win32 stuff. Yea, looking at it, I'm going to try to reuse as much of the command line code as possible to keep things as the 'same' as possible. The primary difference is I can easily multithread the backend, and keep it seperate from the UI.. ;-P > HTTP/1.1 > Yup, that's right... let's use HTTP/1.1! It already has EVERYTHING needed > to handle any type of file transfer, and it's commonplace, and it works. > Here's how, simple version: > user x sending file to user z > z recieves message and uses HTTP/1.1 to GET file Only one problem (Which someone else has already pointed out.. Yes, I cheat and read ahead.. ;-P). This make a client to client connection, and broadcasts the IP address to clients. I know, you're addressing it via a transport. (Notice the other message regarding transport overload, as well, though).. > Ok, benifits: > HTTP/1.1 can do resumes if it get's broken. > ICQ/AIM transports could impliment "translator" daemons for it > Recieving client could just spawn browser to fetch file > Happens in background, leaves Jabber connection to work normally > This could be simply a URL message, not specific for files I like it.. For ordinary file transfers, and a transport of some sort, this would be wonderful. > A special module could be written on the Jabber server to use this > functionaliy for a "file archive". The client would send a jabber message > to the module and ask for a repository, this would be configurable > obviously so only special users could use it or have size limits. The > module would reply with an: http://serverIPaddress:port/. The client > would then PUT files up there via HTTP, and authenticate them with the > users username/password. Then it would send out the location to GET them > like any other file message as above. This would allow you to send files > to offline users, as well as send files to groups of users, just upload it > once and they all download it. It is also a solution for transferring > files if you are going through a firewall. Actually, it could end up just > being a normal apache and a special module or similiar... and you'd have > your own personal webspace... This I REALLY like.. You could actually automate client upgrades this way, but having a server send out a file get message to users clients who have 'registered' with a transport to recieve update file announcements. Heck, a company could use features like this to use jabber client/server as their 'support' system fairly easily. Build in basic jabber support into the program, and users can communicate via jabber for technical support, file upgrades, new announcements, etc.. > There are some issues here yet, but I think this is the best way to go in > some form. I've really gotta sit down and think this through clearly and > get it written down, but hopefully this will get the discussion started :) Please do.. I LOVE the idea itself, but I can still see holes that needs to be addressed. -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" From owner-jdev@jabber.org Mon Mar 29 15:01:55 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id PAA10735 for jdev-list; Mon, 29 Mar 1999 15:01:55 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id PAA10732 for ; Mon, 29 Mar 1999 15:01:53 -0600 Received: by xavier.ups.com (8.9.1a/8.9.1/UPS) id QAA25864 for jdev@jabber.org; Mon, 29 Mar 1999 16:01:17 -0500 (EST) Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id QAA25829 for ; Mon, 29 Mar 1999 16:01:14 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id QAA11708 for ; Mon, 29 Mar 1999 16:01:13 -0500 (EST) From: "Thomas Charron" To: "Jabber Development" Subject: [JDEV] common libs bug.. Date: Mon, 29 Mar 1999 16:24:17 -0500 Message-ID: <000001be7a2a$808ea640$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Found a small bug in io.c of the lib directory. Around line 54, there is something like this: while(c_count != NULL) { if(FD_ISSET(c_count->id, &read_fd_set)) { Upon initial connection, c_count IS valid, but c_count-> is NOT. Example is in jabber.transport. Start it up telnet to host port 5222, and type . jabber.transport reports the invalid XML header, and dies a terribly.. ;-P -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" From owner-jdev@jabber.org Mon Mar 29 18:13:29 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id SAA11599 for jdev-list; Mon, 29 Mar 1999 18:13:29 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id SAA11596 for ; Mon, 29 Mar 1999 18:13:25 -0600 Received: by xavier.ups.com (8.9.1a/8.9.1/UPS) id TAA18655 for jdev@jabber.org; Mon, 29 Mar 1999 19:12:44 -0500 (EST) Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id TAA17600 for ; Mon, 29 Mar 1999 19:11:20 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id TAA16026 for ; Mon, 29 Mar 1999 19:10:42 -0500 (EST) From: "Thomas Charron" To: "Jabber Development" Subject: [JDEV] CVS Question.. Date: Mon, 29 Mar 1999 19:33:44 -0500 Message-ID: <000001be7a44$f7e07600$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org This should PROBRABLY only go to jeremie, but I'll throw it out to everyone.. ;-P Actually, there are 2 questions: 1) Can you add DIRECTORIES to .cvsignore? 2) I will also need to include .ico files in the clients/win32/res. Will I need to add a -kb for those particular files? Actually, I just thought of a 3rd question.. 3) Will cvs update automatically add new files and directories, or do I specifically need to cvs add them? -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" From owner-jdev@jabber.org Mon Mar 29 19:48:10 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id TAA12151 for jdev-list; Mon, 29 Mar 1999 19:48:10 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from olaf.nick.org (nkirsch@nicholas-kirsch2.ups.edu [209.181.136.247]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id TAA12148 for ; Mon, 29 Mar 1999 19:48:08 -0600 Received: from localhost (nkirsch@localhost) by olaf.nick.org (8.9.1/8.9.1) with ESMTP id RAA25014 for ; Mon, 29 Mar 1999 17:48:30 -0800 Date: Mon, 29 Mar 1999 17:48:30 -0800 (PST) From: "Nicholas M. Kirsch" To: Jabber Development Subject: Re: [JDEV] CVS Question.. In-Reply-To: <000001be7a44$f7e07600$62205e0a@tarot.telecom.ups.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org Since I setup the CVS repository, I will try to answer your questions. 1. I don't believe you can. You can check in the CVS documentation for a more concrete answer, but all my experiences tells me no. 2. I believe a -ko & -kb would be necessary. -ko prevents expansion of keywords (RCS tags) and -kb marks the file as binary. You should only need to do this when initially adding the file, as far as I can remember. 3. You need to manually add directories and files. When you run cvs update, CVS will inform you of an unknown file by putting a question mark in front of it. Hope that helps. Nicholas Kirsch nkirsch@olaf.nick.org On Mon, 29 Mar 1999, Thomas Charron wrote: > This should PROBRABLY only go to jeremie, but I'll throw it out to > everyone.. ;-P > > Actually, there are 2 questions: > > 1) Can you add DIRECTORIES to .cvsignore? > > 2) I will also need to include .ico files in the clients/win32/res. Will I > need to add a -kb for those particular files? > > Actually, I just thought of a 3rd question.. > > 3) Will cvs update automatically add new files and directories, or do I > specifically need to cvs add them? > > -- > Thomas Charron > United Parcel Service > Northeast Region > "Moving at the speed of a T3 Trunk Line!" > From owner-jdev@jabber.org Tue Mar 30 11:20:49 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id LAA15914 for jdev-list; Tue, 30 Mar 1999 11:20:49 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id LAA15911 for ; Tue, 30 Mar 1999 11:20:44 -0600 Received: by xavier.ups.com (8.9.1a/8.9.1/UPS) id LAA13284 for jdev@jabber.org; Tue, 30 Mar 1999 11:20:05 -0500 (EST) Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id LAA13126 for ; Tue, 30 Mar 1999 11:19:42 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id LAA13133 for ; Tue, 30 Mar 1999 11:19:39 -0500 (EST) From: "Thomas Charron" To: Subject: [JDEV] .cvsignore directories.. Date: Tue, 30 Mar 1999 11:42:43 -0500 Message-ID: <000101be7acc$554d5100$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: Importance: Normal Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > 1. I don't believe you can. You can check in the CVS documentation for a > more concrete answer, but all my experiences tells me no. Just found the answer in the FAQ. You CAN add directory names in the ..cvsignore file just as you can directories.. -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" > > 2. I believe a -ko & -kb would be necessary. -ko prevents expansion of > keywords (RCS tags) and -kb marks the file as binary. You should only need > to do this when initially adding the file, as far as I can remember. > > 3. You need to manually add directories and files. When you run cvs > update, CVS will inform you of an unknown file by putting a question mark > in front of it. > > Hope that helps. > > Nicholas Kirsch > nkirsch@olaf.nick.org > > On Mon, 29 Mar 1999, Thomas Charron wrote: > > > This should PROBRABLY only go to jeremie, but I'll throw it out to > > everyone.. ;-P > > > > Actually, there are 2 questions: > > > > 1) Can you add DIRECTORIES to .cvsignore? > > > > 2) I will also need to include .ico files in the > clients/win32/res. Will I > > need to add a -kb for those particular files? > > > > Actually, I just thought of a 3rd question.. > > > > 3) Will cvs update automatically add new files and > directories, or do I > > specifically need to cvs add them? > > > > -- > > Thomas Charron > > United Parcel Service > > Northeast Region > > "Moving at the speed of a T3 Trunk Line!" > > > From owner-jdev@jabber.org Tue Mar 30 13:05:54 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id NAA16540 for jdev-list; Tue, 30 Mar 1999 13:05:54 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from mailhost.communities.com (taken2.communities.com [205.162.51.50] (may be forged)) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id NAA16537 for ; Tue, 30 Mar 1999 13:05:52 -0600 Received: from [205.162.51.192] (carlsmack.communities.com [205.162.51.192]) by mailhost.communities.com (8.9.1/8.9.1) with ESMTP id KAA25621 for ; Tue, 30 Mar 1999 10:08:20 -0800 Message-Id: <199903301808.KAA25621@mailhost.communities.com> X-Mailer: Microsoft Outlook Express for Macintosh - 4.0a (190) Date: Tue, 30 Mar 1999 10:08:38 -0800 Subject: [JDEV] Speaking of firewalls.... From: "Carl MacDonald" To: jdev@jabber.org Mime-version: 1.0 X-Priority: 3 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: 7bit Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org A problem I ran into connecting to my jabber server from home is that our firewall times out idle connections after a period of time. The way I'm getting around this right now is sending a status message every 5 minutes if no traffic has been received from the server. Any thoughts to adding a ping/pong tag to the protocol? Also, I'm using within the tags for some information specific to our product, but what I noticed is that the server escapes anything within the even though it's the tag (I'm still running 0.5 as I haven't been able to get 0.6 to build yet). -- Carl From owner-jdev@jabber.org Tue Mar 30 14:27:06 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id OAA17140 for jdev-list; Tue, 30 Mar 1999 14:27:06 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id OAA17136 for ; Tue, 30 Mar 1999 14:27:00 -0600 Received: by xavier.ups.com (8.9.1a/8.9.1/UPS) id OAA26376 for jdev@jabber.org; Tue, 30 Mar 1999 14:26:18 -0500 (EST) Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id OAA25947 for ; Tue, 30 Mar 1999 14:25:43 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id OAA05341 for ; Tue, 30 Mar 1999 14:25:21 -0500 (EST) From: "Thomas Charron" To: Subject: RE: [JDEV] Speaking of firewalls.... Date: Tue, 30 Mar 1999 14:48:25 -0500 Message-ID: <000001be7ae6$46e48240$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 In-reply-to: <199903301808.KAA25621@mailhost.communities.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of > Carl MacDonald > Subject: [JDEV] Speaking of firewalls.... > A problem I ran into connecting to my jabber server from home is that our > firewall times out idle connections after a period of time. The way I'm > getting around this right now is sending a status message every 5 > minutes if > no traffic has been received from the server. Good idea.. Perhaps a ping message that can be directed directly to the server. Another way to do it would be to have the client send a message to itself, and then intercept it before it get's to the user.. Luckily, this will be easier to do with 06, it's MUCH better then 05 was.. May I ask what problems you've had compiling 06? -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" > > Any thoughts to adding a ping/pong tag to the protocol? > > Also, I'm using within the tags for some > information specific > to our product, but what I noticed is that the server escapes anything > within the even though it's the tag (I'm still > running 0.5 as > I haven't been able to get 0.6 to build yet). > > -- > Carl > From owner-jdev@jabber.org Tue Mar 30 17:33:52 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id RAA18123 for jdev-list; Tue, 30 Mar 1999 17:33:52 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id RAA18093 for ; Tue, 30 Mar 1999 17:28:57 -0600 Received: by xavier.ups.com (8.9.1a/8.9.1/UPS) id RAA26893 for jdev@jabber.org; Tue, 30 Mar 1999 17:27:05 -0500 (EST) Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id RAA26614 for ; Tue, 30 Mar 1999 17:26:51 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id QAA03536 for ; Tue, 30 Mar 1999 16:51:45 -0500 (EST) From: "Thomas Charron" To: "Jabber Development" Subject: [JDEV] Win32 Client Executable? Date: Tue, 30 Mar 1999 17:14:51 -0500 Message-ID: <000001be7afa$bc141d00$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I have a a quick question.. Do you want a copy of the Win32 JabberClient.exe file to be INCLUDED in CVS? It is currently approximatly 100k. Currently, it's looking like the win32 client directory will take up 300k in CVS, mainly due to the inclusion on the expat .lib and .dll files. In the near future, it will include the expat package as part of the build, but for now I'm linking against the expat dll's for simplicity's sake. When I do, I can remove the DLL's and lib files.. -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" From owner-jdev@jabber.org Tue Mar 30 17:39:35 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id RAA18162 for jdev-list; Tue, 30 Mar 1999 17:39:35 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id RAA18147 for ; Tue, 30 Mar 1999 17:37:59 -0600 Received: by xavier.ups.com (8.9.1a/8.9.1/UPS) id RAA02591 for jdev@jabber.org; Tue, 30 Mar 1999 17:35:23 -0500 (EST) Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id RAA02233 for ; Tue, 30 Mar 1999 17:34:44 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id RAA20033 for ; Tue, 30 Mar 1999 17:34:40 -0500 (EST) From: "Thomas Charron" To: "Jabber Development" Subject: [JDEV] Requested change to xpt.c Date: Tue, 30 Mar 1999 17:57:47 -0500 Message-ID: <000101be7b00$bbf589c0$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I have a bit of a problem with xpt.c. Visual C++ complains about the str var in expat_charData. It wants the char dec to be a constant: --- void expat_charData(void *userData, const char *s, int len) { xptpool *xp = userData; xpt *x; char str[len + 1]; --- Could we change the --- char str[len + 1]; --- to --- char *str; str = malloc(len + 1); --- -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" From owner-jdev@jabber.org Tue Mar 30 20:21:40 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id UAA18869 for jdev-list; Tue, 30 Mar 1999 20:21:40 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id UAA18866 for ; Tue, 30 Mar 1999 20:21:38 -0600 Received: by xavier.ups.com (8.9.1a/8.9.1/UPS) id UAA20648 for jdev@jabber.org; Tue, 30 Mar 1999 20:21:06 -0500 (EST) Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id UAA20629 for ; Tue, 30 Mar 1999 20:21:04 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id LAA11870 for ; Tue, 30 Mar 1999 11:16:58 -0500 (EST) From: "Thomas Charron" To: Subject: RE: [JDEV] CVS Question.. Date: Tue, 30 Mar 1999 11:40:01 -0500 Message-ID: <000001be7acb$f4db11e0$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: Importance: Normal Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of > Nicholas M. Kirsch > Subject: Re: [JDEV] CVS Question.. > 1. I don't believe you can. You can check in the CVS documentation for a > more concrete answer, but all my experiences tells me no. Well, since I have to manually add directories in the cvs source tree, I can simply not add the directories. Visual C++ creates a 'Release' and/or 'Debug' directory, depending on what type of compile, which you'd NOT want in the source tree.. It'll just mean I'll get ?'s on those directories, so not a problem there.. > 2. I believe a -ko & -kb would be necessary. -ko prevents expansion of > keywords (RCS tags) and -kb marks the file as binary. You should only need > to do this when initially adding the file, as far as I can remember. That's what I got out of it as well.. > 3. You need to manually add directories and files. When you run cvs > update, CVS will inform you of an unknown file by putting a question mark > in front of it. > Hope that helps. Yep, exactly what I wanted to know.. Hopefully tonight there will be a bunch-o-checkins in the Win32 directory.. -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" > > Nicholas Kirsch > nkirsch@olaf.nick.org > > On Mon, 29 Mar 1999, Thomas Charron wrote: > > > This should PROBRABLY only go to jeremie, but I'll throw it out to > > everyone.. ;-P > > > > Actually, there are 2 questions: > > > > 1) Can you add DIRECTORIES to .cvsignore? > > > > 2) I will also need to include .ico files in the > clients/win32/res. Will I > > need to add a -kb for those particular files? > > > > Actually, I just thought of a 3rd question.. > > > > 3) Will cvs update automatically add new files and > directories, or do I > > specifically need to cvs add them? > > > > -- > > Thomas Charron > > United Parcel Service > > Northeast Region > > "Moving at the speed of a T3 Trunk Line!" > > > From owner-jdev@jabber.org Wed Mar 31 09:25:02 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id JAA21839 for jdev-list; Wed, 31 Mar 1999 09:25:02 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from localhost (jeremie@localhost) by mondo.eppg.com (8.8.7/8.8.7) with SMTP id JAA21834 for ; Wed, 31 Mar 1999 09:25:00 -0600 Date: Wed, 31 Mar 1999 09:24:59 -0600 (EST) From: Jeremie X-Sender: jeremie@mondo.eppg.com To: Jabber Development Subject: Re: [JDEV] Concern regarding transport overload.. In-Reply-To: <000801be7a1c$7ba2eaa0$62205e0a@tarot.telecom.ups.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > > How many 'transports' are we going to have on a basic server. I think that > a basic server should be able to support several of the things that we've > all said would be best in a module, but I'm concerned about people needing > to run 10 DIFFERENT transport programs to supply this functionality. Would > it be possible for the basic jabber.transport to be able to provide these > abilities without needing to run all of these transports? Ooohhh... I see a minor confusion here :) A 'transport' is quite different than a 'module'. The transport is a completely seperate 'server' process that understands the server <-> server Jabber protocol and can translate to another messaging service OR serve a special function/purpose. The Jabber transport, which is just a normal transport, is what the Jabber clients connect to, it's where most of the work happens. A 'module' is an extension to the Jabber transport, similiar to how modules work in Apache. The modules inside the Jabber transport are what handles most of the end-user server-side intelligence, making decisions for the user and storing their data. There will probably be at least a few transports installed/running with any installation, mostly to supply the transparent connectivity to ICQ/AIM. But it will work just fine with only the one Jabber transport. I'd love to see a very rich pool of transports available for those that want different functionality. With modules though, they are compiled in and any installation will probably only use a few, the ones that have the functionality they need. Either way, lots of transports and lots of modules is a good thing, not all installed at once, but available to cover different areas of needs. > Now, don't get me wrong, I LIKE being able to throw everything in modules. > What I'm concerned about is the one or two executable ISP installs that have > been mentioned.. Any ideas on how we can have the best of both worlds? I'd like to actually have a completely different codebase(sharing the common libs of course) to handle the special ISP server, one that is lean and requires no setup/config, and that is limited in functionality available. If they hit a point where they want more functionality, upgrade, but this gives them an easy way to try it out and make it available NOW without worry. It wouldn't be that hard of a build to do, but it would be a forking off of the main codebase, and I'll wait till that main codebase is foundationally stable and fairly complete before doing so. Jer From owner-jdev@jabber.org Wed Mar 31 09:43:53 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id JAA21970 for jdev-list; Wed, 31 Mar 1999 09:43:53 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from localhost (jeremie@localhost) by mondo.eppg.com (8.8.7/8.8.7) with SMTP id JAA21967 for ; Wed, 31 Mar 1999 09:43:51 -0600 Date: Wed, 31 Mar 1999 09:43:51 -0600 (EST) From: Jeremie X-Sender: jeremie@mondo.eppg.com To: jdev@jabber.org Subject: Re: [JDEV] Speaking of firewalls.... In-Reply-To: <199903301808.KAA25621@mailhost.communities.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > A problem I ran into connecting to my jabber server from home is that our > firewall times out idle connections after a period of time. The way I'm > getting around this right now is sending a status message every 5 minutes if > no traffic has been received from the server. I've seen similiar things... many things like to drop idle TCP connections, which seems naughty but it happens, so... > Any thoughts to adding a ping/pong tag to the protocol? Yes, many :) It's going to need this for one primary reason, TCP doesn't know to drop the connection when the other end "dissappears", such as a dialup connection breaking and not disconnecting properly. There is a built in KEEPALIVE available for TCP connections, but vendor implementations are way to flaky to make it useful. TCP _does_ drop the connection if the server sends data though. Apparently you can send NULL's, err, absolutely empty TCP packets that will cause the normal two way TCP traffic over a connection. But I haven't tried it yet, so I don't know that for sure. If it works as I understand it, I'll have the server create this activity on the connection at a regular interval. This shouldn't require any changes on the clients end of things. > Also, I'm using within the tags for some information specific > to our product, but what I noticed is that the server escapes anything > within the even though it's the tag (I'm still running 0.5 as > I haven't been able to get 0.6 to build yet). Yes, that's a 0.5 thing(everything outgoing was escaped). 0.6 will allow you to put normal XML tags inside the and they will be passed through as XML tags. Jer From owner-jdev@jabber.org Wed Mar 31 09:49:15 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id JAA22052 for jdev-list; Wed, 31 Mar 1999 09:49:15 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from localhost (jeremie@localhost) by mondo.eppg.com (8.8.7/8.8.7) with SMTP id JAA22049 for ; Wed, 31 Mar 1999 09:49:13 -0600 Date: Wed, 31 Mar 1999 09:49:13 -0600 (EST) From: Jeremie X-Sender: jeremie@mondo.eppg.com To: Jabber Development Subject: Re: [JDEV] Win32 Client Executable? In-Reply-To: <000001be7afa$bc141d00$62205e0a@tarot.telecom.ups.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > I have a a quick question.. Do you want a copy of the Win32 > JabberClient.exe file to be INCLUDED in CVS? It is currently approximatly > 100k. CVS is mostly for sources, so maybe not... on the other hand, it would be nice to have it handy for regular testing... I guess, try it and we'll go from there... it's always easy to remove if it's a problem. Maybe we can set up a special ftp repository for binary builds :) Jer From owner-jdev@jabber.org Wed Mar 31 11:06:50 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id LAA22586 for jdev-list; Wed, 31 Mar 1999 11:06:50 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id LAA22583 for ; Wed, 31 Mar 1999 11:06:47 -0600 Received: by xavier.ups.com (8.9.1a/8.9.1/UPS) id LAA21097 for jdev@jabber.org; Wed, 31 Mar 1999 11:06:14 -0500 (EST) Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id LAA21026 for ; Wed, 31 Mar 1999 11:06:08 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id LAA19943 for ; Wed, 31 Mar 1999 11:06:04 -0500 (EST) From: "Thomas Charron" To: Subject: RE: [JDEV] Concern regarding transport overload.. Date: Wed, 31 Mar 1999 11:29:08 -0500 Message-ID: <000101be7b93$9a0ced60$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of > Jeremie > Subject: Re: [JDEV] Concern regarding transport overload.. > I'd like to actually have a completely different codebase(sharing the > common libs of course) to handle the special ISP server, one that is lean > and requires no setup/config, and that is limited in functionality > available. If they hit a point where they want more functionality, > upgrade, but this gives them an easy way to try it out and make it > available NOW without worry. I can provide this as an NT service with little problem.. ot right NOW, mind you, but it'd be relitivly simple.. > Ooohhh... I see a minor confusion here :) Yep, there was.. ;-P > A 'transport' is quite different than a 'module'. The transport is a > completely seperate 'server' process that understands the server <-> > server Jabber protocol and can translate to another messaging service OR > serve a special function/purpose. Ahh, see, in the past we've always refered to it as 'In A Transport', so I imagined several DIFFERENT transports, one for each type.. ;-P -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" From owner-jdev@jabber.org Wed Mar 31 16:45:27 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id QAA24572 for jdev-list; Wed, 31 Mar 1999 16:45:27 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from olaf.nick.org (nicholas-kirsch2.ups.edu [209.181.136.247]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id QAA24567 for ; Wed, 31 Mar 1999 16:45:24 -0600 Received: from localhost (nkirsch@localhost) by olaf.nick.org (8.9.1/8.9.1) with ESMTP id NAA11761 for ; Wed, 31 Mar 1999 13:45:32 -0800 Date: Wed, 31 Mar 1999 13:45:32 -0800 (PST) From: "Nicholas M. Kirsch" To: Jabber Development Subject: Re: [JDEV] Win32 Client Executable? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I'm thinking maybe we should include the executable for a Win32 client in the CVS repository, until we have a dedicated ftp site for binaries. Whereas C compilers for UNIX are easy to find, the same does not apply for Win32. I would like to try out the client the next time I come across a box, but I surely am not going to obtain Visual C to do it.. :) Nick On Wed, 31 Mar 1999, Jeremie wrote: > > > > I have a a quick question.. Do you want a copy of the Win32 > > JabberClient.exe file to be INCLUDED in CVS? It is currently approximatly > > 100k. > > CVS is mostly for sources, so maybe not... on the other hand, it would be > nice to have it handy for regular testing... > > I guess, try it and we'll go from there... it's always easy to remove if > it's a problem. Maybe we can set up a special ftp repository for binary > builds :) > > Jer > From owner-jdev@jabber.org Wed Mar 31 18:07:30 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id SAA25065 for jdev-list; Wed, 31 Mar 1999 18:07:30 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id SAA25062 for ; Wed, 31 Mar 1999 18:07:27 -0600 Received: from xavier.ups.com (localhost [127.0.0.1]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id SAA24889 for ; Wed, 31 Mar 1999 18:06:54 -0500 (EST) Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id RAA05459 for ; Wed, 31 Mar 1999 17:32:00 -0500 (EST) Received: from revere2.telecom.ups.com (localhost [127.0.0.1]) by revere2.telecom.ups.com (8.8.7/UPS) with ESMTP id RAA05535 for ; Wed, 31 Mar 1999 17:31:57 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id RAA05528 for ; Wed, 31 Mar 1999 17:31:57 -0500 (EST) From: "Thomas Charron" To: "Jabber Development" Subject: [JDEV] Another requested source change.. Date: Wed, 31 Mar 1999 17:55:10 -0500 Message-ID: <000101be7bc9$87e30e40$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org I have another requested source change, this time for the include files in lib. If you want me to use my OWN versions of these files, I can do that, but in order to use the current ones, I need these changes made: -------common.h These include files need to be #ifndef WIN32'd, as they do not apply to Visual C++, and don;t event exist under it, for that matter.. strings.h unistd.h sys/socket.h netinet/in.h netdb.h arpa/inet.h This include file is actually just , instead of sys/time.h = time.h ---common_functions.h These need to be #ifndef WIN32. I'm not using your networking, and compiler doesn't like them much.. ;-P make_netsocket make_addr Again, if you want me to use COPIES of the include files in the win32 directory, I have NO problem with doing that. -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!" From owner-jdev@jabber.org Wed Mar 31 18:39:24 1999 Received: (from majordomo@localhost) by mondo.eppg.com (8.8.7/8.8.7) id SAA25279 for jdev-list; Wed, 31 Mar 1999 18:39:24 -0600 X-Authentication-Warning: mondo.eppg.com: majordomo set sender to owner-jdev@jabber.org using -f Received: from xavier.ups.com (xavier.ups.com [198.80.14.117]) by mondo.eppg.com (8.8.7/8.8.7) with ESMTP id SAA25276 for ; Wed, 31 Mar 1999 18:39:21 -0600 Received: from xavier.ups.com (localhost [127.0.0.1]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id RAA00038 for ; Wed, 31 Mar 1999 17:25:31 -0500 (EST) Received: from revere2.telecom.ups.com (smtp.field2.ups.com [153.2.0.50]) by xavier.ups.com (8.9.1a/8.9.1/UPS) with ESMTP id RAA28532 for ; Wed, 31 Mar 1999 17:23:47 -0500 (EST) Received: from revere2.telecom.ups.com (localhost [127.0.0.1]) by revere2.telecom.ups.com (8.8.7/UPS) with ESMTP id RAA01580 for ; Wed, 31 Mar 1999 17:23:45 -0500 (EST) Received: from tarot.telecom.ups.com ([10.94.32.98]) by revere2.telecom.ups.com (8.8.7/UPS) with SMTP id RAA01576 for ; Wed, 31 Mar 1999 17:23:44 -0500 (EST) From: "Thomas Charron" To: Subject: RE: [JDEV] Win32 Client Executable? Date: Wed, 31 Mar 1999 17:46:58 -0500 Message-ID: <000001be7bc8$6230e600$62205e0a@tarot.telecom.ups.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-jdev@jabber.org Precedence: bulk Reply-To: jdev@jabber.org > From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of > Nicholas M. Kirsch > Subject: Re: [JDEV] Win32 Client Executable? > I'm thinking maybe we should include the executable for a Win32 client in > the CVS repository, until we have a dedicated ftp site for binaries. > Whereas C compilers for UNIX are easy to find, the same does not apply for > Win32. I would like to try out the client the next time I come across a > box, but I surely am not going to obtain Visual C to do it.. Exactly why I asked.. Now that I've got it compiling without needing to use the expat DLL's, I can do it without much of a problem.. -- Thomas Charron United Parcel Service Northeast Region "Moving at the speed of a T3 Trunk Line!"