scroll-seq hard codes a "1m" scroll duration, this should probably be parameterized so it can be overridden.

[Dave Tenny]

These scroll windows have performance and correctness/failure implications, so should be user selectable.  Ideally it would take its default value from the search response passed into scroll-seq, but I haven't peeked to see if that data is available (i.e. if the search response echos the scroll timeout in the original search request).