reading argus files using non-sequential access

[Mark Poepping]

How would byte offset be more valuable than time-offset?  Does it end up
being much faster?
Mark.

> -----Original Message-----
> From: argus-info-bounces at lists.andrew.cmu.edu [mailto:argus-info-
> bounces at lists.andrew.cmu.edu] On Behalf Of Carter Bullard
> Sent: Wednesday, January 31, 2007 9:36 PM
> To: Argus
> Subject: [ARGUS] reading argus files using non-sequential access
> 
> Gentle people,
> All ra* programs have the ability to read argus files using starting
> and ending byte offsets.  If you have a list of offsets, this type
> of feature can make processing large argus files very fast/efficient.
> 
> The syntax for reading files using offsets has been/is/will be/could be:
>    "-r file::ostart:oend"
> 
> (or at least that is how I've implemented it in the past)
> where ostart is the starting offset, and oend is the ending offset.
> 
> This is not a useful feature if you don't know where the record
> boundaries are in the file, so I haven't 'exposed' this feature yet, but
> I think that it is something that we can begin to work with, or at
> least talk about how we could use it.
> 
> Anyone interested in this type of feature and would like to
> talk about how we could use this?
> 
> Carter
> 
> 
> 
> 
> 
> 
> 
>