[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tired of waiting

To: Erik Ostrom <eostrom@research.att.com>
Subject: Re: tired of waiting
From: "Jay A. Carlson" <nop@kagoona.mitre.org>
Date: Thu, 24 Apr 1997 16:42:27 -0400
cc: Dave Kormann <davek@research.att.com>, mcp-dev@research.att.com
In-reply-to: Your message of "Thu, 24 Apr 1997 14:48:56 EDT." <199704241848.OAA00183@radish.research.att.com>

> > > That's incorrect, I think.  Messages are presently network-newline 
> > > separated records of printable ASCII (well plus space and tab) 
> > > characters.  I skipped this problem in my rewrite by simply claiming 
> > > that framing was defined elsewhere.
> > 
> > ok, i'll fix this.
> 
> Can we not include tab?  Jay, do you use tab?

Hell no.  I still want to take tab out of the moo charset.

> > > Also, we use #$#mcp version: 2.0 [to: 2.1] for our keywords as this 
> > > is a little less annoying to telnet-only users.
> > 
> > erp, i'm not sure that i buy this, but in any case, would it be
> > possible to beat you into compliance?
> 
> Yeah, would it?  Or do we have to go to 3.0?  (Common MCP: The Language.)

I'll have to stare at what we're doing and make sure our deployed
mcp-1 implementations don't lose badly.  I guess I dunno why YOU get
to beat ME into compliance instead of vice versa....I suppose actually
starting the process up again gets you some points.

Jay Carlson   nop@kagoona.mitre.org    nop@nop.com
The MITRE Corporation, Bedford MA

Flat text is just *never* what you want.       ---stephen p spackman

Follow-Ups:
- practical matters (was Re: tired of waiting)
  - From: Erik Ostrom <eostrom@research.att.com>

Prev by Date: Re: latest update, then.
Next by Date: practical matters (was Re: tired of waiting)
Prev by thread: tired of waiting
Next by thread: practical matters (was Re: tired of waiting)
Index(es):
- Date
- Thread