Gah, too much screw choice

Still the fault of the newsreader if it doesn't wait for a response.

Then all of the common newsreaders are broken by your definition.

They all wait for a response. The time they wait before assuming that the send attempt has failed due to a transmission problem is configurable, and the response to such a failure can also sometimes be configured, but may well be hard coded. Most newsreaders are single threaded, and so cannot be used to read messages while waiting for the server to respond, so you have to decide on a compromise between hanging round waiting for responses and reading other messages.

I use aioe.org, and my newsreader has never sent multiple posts. And I can certainly use it while it is posting or waiting to post or receive. It uses a separate transport for that. Which also manages to know if a post has been sent successfully.

Says Mr Nice Fast Urban Broadband...

I've not done a speed test at the time mine does it, but I'd hazard a guess that I'm getting a chunk under 500kbit.

Not really to do with being on broadband I think, more they way the setup works. I used Usenet on dialup and then 512k broadband for a number of years

I don't I've ever had a post sent multiple time by my newsreader, and I can also read and post stuff whilst it's dealing with sending and collecting news.

I use Turnpike, and the news posting and collecting is handled by an a separate program from the reading.

Only downlaoding the headers to start with, rather than the full message, will put more overhead on the system when reading as well.

No - I was using the same software on dialup. Written by those who understand Usenet - which rules out MS.

Think what it does is talk to the other end.

'Are you ready to receive a message? No? Ok - I'll leave it till later.'

She was blonde. And I am thinking of asking her to marry me.

Back in the day, when they were typical connections. I suspect that the combo of newer-version software "expecting" faster connections and the increasing flakiness of semi-orphaned and unloved news servers is contributing.

"Did you get that OK?" "Soddit, I'll resend"

There are tow possibles to 'are you ready?'

One is the sound of silence, the other is 'no'.

How long you listen to the sound of silence is a moot point.

Generally on today's internet anything more the a second is 'time out'

Reminds me of a long ago afternoon in childhood when my elder sisters and their odd friends were playing the balcony scene from Romeo and Juliet, largely because the friends had a balcony...

"Wherefore art thou, Rom-ee-o?" (repeated twice) 'Oh just hang ON, I'm behind a bush doing something.'

On Thursday 21 November 2013 17:38 Adrian wrote in uk.d-i-y:

I've not noticed anything in general terms - and I'm using tethered 3G quite a lot on the train to read news.

Tethered 3G makes 57000 baud modem links look *good* most of the time. Sure, it peaks at several Mbps on a good day. In a few minutes you can be down to bugger all and packet round-trip times of several MINUTES (I kid you not - I leave ping running in a terminal so I can see when the signal gets good and quickly do stuff before the next tunnel.

On Thursday 21 November 2013 18:31 The Natural Philosopher wrote in uk.d-i- y:

You've overlooked 3G (my other recent post in this thread).

A man's internet connection on 3G now makes what we had in the 90's look like an example of rock solid stability.

In fact, 3G really shows how well TCP was designed.

TB here is set for 30 seconds. It's also set to put a message up on screen telling me the send attempt has failed and would I like to try again? I've never suffered from the multiple posting problem, even with bad TACS conditions, Which might let you guess how long I've been playing this game.

What happened to 'yes'?

If no response, no point in sending the post.

Often takes rather longer than that here as regards email and news.