home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!uvaarpa!darwin.sura.net!paladin.american.edu!auvm!IS.RICE.EDU!DBOYES
- X-Mailer: ELM [version 2.3 PL11]
- Message-ID: <9209042223.AA03974@brazos.is.rice.edu>
- Newsgroups: bit.listserv.cw-email
- Date: Fri, 4 Sep 1992 17:23:30 CDT
- Sender: Campus-Wide Electronic Mail Systems discussion list
- <CW-EMAIL@TECMTYVM.BITNET>
- From: David E Boyes <dboyes@IS.RICE.EDU>
- Subject: Re: MIME (E-mail and calendaring recommendations)
- In-Reply-To: <9209042213.AA17909@moe.rice.edu>; from "bleimeyr@woz.mayo.edu"
- at Sep 4, 92 5:08 pm
- Lines: 24
-
- > I thought that Paul Lindner at the University of Minnesota Gopher
- > team had produced some example code using the chronos protocol.
- > Perhaps it went no further. Seemed like a good idea though.
-
- Yes, Paul did produce a prototype server, but it was for a very
- early version of the protocol, and doesn't really reflect the
- current state of the protocol at all. I have Paul's code, and am
- planning to try to bring it up to the current protocol
- specification, but I'd like to try and coordinate some more
- extensive help in turning it into a real service.
-
- I'd intended on developing the clients using the STDWIN package
- from a site in the Netherlands. STDWIN would allow the same
- source to be used for a curses-style Unix client, an X client, a
- MacOS client, and a MS Windows client. I don't know whether
- STDWIN has been enhanced to support OS/2 v2 yet, but the Windows
- support should suffice. For CMS, I intended to use TNT or
- CUA2001, but may be forced to go back to doing my own CMS Windows
- code, as IBM has withdrawn TNT, and CUA2001 is impossibly
- expensive. Another possibility is to develop a MIME and Gopher
- interface to the chronos server -- it'd be neat for doing things
- like moving information between organizations.
-
- > Robert R. Bleimeyer Internet: bleimeyer@mayo.edu
-