Re: query vs request

[Peter <pnewman1 -at- home -dot- com>]

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. 
-- 
Peter

"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 http://www.ehelp.com/techwr. 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 
http://www.raycomm.com/techwhirl/ for more resources and info.