Re: query vs request

Subject: Re: query vs request
From: Peter <pnewman1 -at- home -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Thu, 21 Feb 2002 07:38:46 -0500

Steve Hudson wrote:
> Dear Raeleeny,
> Kerr-ect. All of those are not only networking terms, but more specifically,
> comms protocols. As they are such, they must support queries and answers. I
> guess it's all hair-splitting, but if you really wanted to be pedantic, you
> would use Query for database matters only, and leave it as request for
> everything else. (Request <network object>) Ideally every request gets ack'd
> or nak'd, failure to nak successively leads to outages :-)
> GET, PUT and POST are the methods to support requests. Just about everyone
> will have a different take on it though, so define your terms in the start
> of the manual and just go for it.

I should modify my prior answer. Requests deal with demand for services:
printer; server; etc. The term is not limited to networking.

"When a man sits with a pretty girl for an hour, it seems like a
minute. But let him sit on a hot stove for a minute-and it's
longer than any hour. That's relativity,"
- Einstein-

Did you know you can get RoboHelp certified?
To learn how, visit Be sure to also check out
our special pricing offers and promotions for RoboHelp 2002.

You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit for more resources and info.


RE: query vs request: From: Steve Hudson

Previous by Author: Re: query vs request
Next by Author: Re: Tired of giving out technical advice for free
Previous by Thread: RE: query vs request
Next by Thread: RE: query vs request

What this post helpful? Share it with friends and colleagues:

Sponsored Ads