Hi Lauren,
Thanks for your relpy.
Not exactly, I want to handle that 'path-index' functionality separately from OW.
I was hoping I could write a servlet to act as the remote resource store to OW, which will look up the warc location on the fly. I see your point about serving the warcs via a webserver and using the path-index file with URLs. But it seemed nicer (in my head) if I could just serve the warc location via an external service, removing the path-index flat file step altogether.
The context is that we are trying to use OW as a viewer from our preservation system, which has a growing web archive. For a growing collection the remote resource store seemed more of a fit than using a path-index file.
Cheers,
Ben