| The algorithm in V1.2 is the following.
For each request/response we attempt to open as many concurrent links
as is necessary. If the device can't support that number of links we
drop back to single link mode. Thus any single command to a DR 250
in isolation works correctly. However, if for some reason 2 operations
with a DR250 happen to occur at the same time (ie. polling and an
interactive request), then the first one will get the link and succeed
and the second one will get an exception of insufficient resources
from the DR250.
So if you are careful about not having too many concurrent requests
outstanding to a DR250 then V1.2 will resolve your problems.
The above solution was the best compromise we could achieve. It doesn't
make requests to reasonable devices pay a performance penalty while
it allows access to screwball devices like the DR250 but with some
performance penalty.
wally
|