On Fri, 18 Jul 2003 [EMAIL PROTECTED] wrote:
> On Thu, 17 Jul 2003, Alexander R. Pruss wrote:
> > Tim Wentworth had made a local change to his PyPlucker to put in a marker
> > in the reserved byte in the record header to indicate whether the record
> > is continued by the next one.
> >
> > I propose this become official. Specifically, I propose that bit 0 should
> > be 0 if the current record is not continued and 1 if it is continued by
> > the next record in the database. This will let one amalgamate all the
> > fragments. I don't know how these kinds of changes to the format are
> > made. Do we vote?
>
> So this is just to combine fragments? Then it seems reasonable.
> OTH some people have already asked about a more general mechanism
> to link a sequence of pages into a stream (supposedly e.g. lynx does
> this via some standard HTML mechanism). In that case it could become
> awkward to force the parser to output all those pages in the correct
> sequence (and then put images etc. at the end )... Maybe for that it
> would be better to somewhere store an integer. I don't remember the
> record format, but I assume it is not extensible enough to add something
> like this?
We could have each record store the previous fragment record id and the
next fragment record id. That would give us the greatest flexibility. I
just don't know how to go about doing it--where do we fit the four bytes
needed?
Alex
--
Dr. Alexander R. Pruss || e-mail: [EMAIL PROTECTED]
Philosophy Department || online papers and home page:
Georgetown University || www.georgetown.edu/faculty/ap85
Washington, DC 20057 ||
U.S.A. ||
-----------------------------------------------------------------------------
"Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur."
- Paul of Worczyn (1424)
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
