Re: @ character in http login

Jerry Stuckle wrote:
> Michael B. Trausch wrote:
> > Jerry Stuckle wrote in <KtOdnWsKY78PDtbZnZ2dnUVZ_vadnZ2d@comcast.com> on Sun
> > April 23 2006 11:50:
> >
> >>And it's even worse form to criticize someone for repeating the content of
> >>YOUR OWN post 12 minutes after you posted it.
> >>
> >>This is not a "I got the right answer first" contest. This is about
> >>helping each other.
> >>
> >
> >
> > I agree with you on that. Now, I didn't realize that the lag was 12 whole
> > minutes -- that's atypical for many networks these days, even Usenet.
> > Often, I can post something to Usenet and find it on Google Groups within
> > five minutes of my having posted it. Thus, it didn't seem unreasonable to
> > me to prompt Gordon to check prior to posting. It would seem that he is
> > not to blame for not checking; rather, his NNTP spooling service is a bit
> > behind on getting the feeds from Usenet.
> >
> > Looking at their web site, it could also be a slowdown caused by their
> > Usenet spam filtration software or something similar; either way, that's a
> > great deal of lag. :( It isn't the 1980s anymore. <g>
> >
> > - Mike
>
> Not atypical at all, Mike. It all depends on how often usenet servers sync with
> each other, how many servers are between the posting one and the receiving one,
> any network delays which can creep in, and even if a router is temporarily down
> for maintenance.
>
> 12 minutes is nothing. I, too, have regularly seen delays of 2 hours or more.
>
> --
> ==================
> Remove the "x" from my email address
> Jerry Stuckle
> JDS Computer Training Corp.
> jstucklex@attglobal.net
> ==================

Just blame slow typing and everyone get along with your lives.
Received on Mon May 1 03:02:36 2006