| To: | niv@xxxxxxxxxx |
|---|---|
| Subject: | Re: patch for common networking error messages |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Mon, 16 Jun 2003 15:57:17 -0700 (PDT) |
| Cc: | janiceg@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, stekloff@xxxxxxxxxx, girouard@xxxxxxxxxx, lkessler@xxxxxxxxxx, kenistonj@xxxxxxxxxx, jgarzik@xxxxxxxxx |
| In-reply-to: | <3EEE49BA.6070401@xxxxxxxxxx> |
| References: | <3EEE40F1.4030107@xxxxxxxxxx> <20030616.151308.55864910.davem@xxxxxxxxxx> <3EEE49BA.6070401@xxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Nivedita Singhvi <niv@xxxxxxxxxx> Date: Mon, 16 Jun 2003 15:50:34 -0700 I do see positives in the feature as a whole though. Would you design a network protocol this way? By passing strings like "open connection please", "sure no problem" back and forth between server and client? Of course not. So why are we even remotely considering the standardization of _STRINGS_ for event reporting? |
| Previous by Date: | Re: patch for common networking error messages, David S. Miller |
|---|---|
| Next by Date: | Re: Route cache performance tests, Simon Kirby |
| Previous by Thread: | Re: patch for common networking error messages, Nivedita Singhvi |
| Next by Thread: | Re: patch for common networking error messages, Donald Becker |
| Indexes: | [Date] [Thread] [Top] [All Lists] |