| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Confusing terminology |
| Date: | 2002-01-18 20:12:25 |
| Message-ID: | 200201182012.g0IKCP210605@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> While this is certainly project-specific language, it's useful to people
> who may actually have to look at the code; and if they're reading
> documentation that is talking about the parts of the server in the first
> place, they're not that far away from wanting to look at code. I don't
> think that
>
> After receiving a connection request, the server spawns
> a session process to handle that client session.
>
> is an improvement --- it seems more to have reduced the concept to a
> tautology. (Also, as seen here, I don't care for using "session"
> to describe a process. A session is a different sort of animal.)
Yes, I feel session is something that exists between the client and the
server. It is not a server-only concept.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-01-18 20:16:39 | Re: user types API wish list |
| Previous Message | Bruce Momjian | 2002-01-18 20:09:05 | Re: Ignorance time: when is 7.2 due ? |