"Neil Williams" wrote in message
...
"tim....." wrote:

I don't think the time outside the system is critical to causing the
problem here (except in as much as making it possible to transact your
genuine business within the transfer time).

You're just as likely to "time out" on a through journey that "wasn't" if
you spend 15 minutes transferring as 2 minutes.

Maybe if it times out, then, it should be reconstructed as two journeys
split at the last OSI touched. Or can't it do that?

Well of course it should, but currently it can't.

The hard part here is that, theoretically, the journey could include two (or
more) OSIs and there (apparently) isn't enough memory on the card to keep
all of them to calculate the backtracking correctly.

But I don't see that this precludes them implementing a solution that works
automatically for the simple case. There might still be people who can't be
resolved this way, but unless I have thought this through wrongly, this
incorrect set is absolutely a subset of the current incorrect set (and
certain to be very much smaller).

tim