Re: client protocol not responding to repeated checkout request

[Larry Jones]

Alexander Taler writes:
> 
> It's not quite the same if I send the commands using separate
> connections.  I'm not sending any Entry, Modified, Is-modified,
> Unchanged or Questionable requests, so the server has no idea
> what my local state is.  I guess what this means is that the
> server detects that there is no change from the last
> update/checkout that it gave me, so no need to resend.

Although the server doesn't know what your local state is, it *does*
know what *its* local state is.  When you do a checkout, for example,
the server actually does a checkout into a temp directory and then sends
you the resulting files.  When you do another checkout, the server again
does a checkout into the same temp directory and nothing changes, so it
doesn't send you anything.

-Larry Jones

It COULD'VE happened by accident! -- Calvin