Re: iSCSI: Iterating long text responses

[Stephen Bailey <steph@cs.uchicago.edu>]

Mark,

> Anyway, #2 would work fine as well, but again, I'd really like
> to avoid keeping state on the target.

You have to keep state on lots of state at this granularity (per
session/connection) on the target anyway.  All this would require is
an integer index into your target list table (which you obviously have
in some form to respond to SendTargets at all...)

One might suggest a variant of #5 with an initial offset argument to
the request, so you could get `what's left', but that really does
create a state problem.  With the simple iterator at least you know
that every return is (or was) a complete target description.

But then again, what do I know?  [this list is like driving, cf. Repo
Man]

Certainly doing #5 would not leave a criminal hole in the spec.
Neither would it probably be used in general by X-* operations.

Steph