I have been fiddling w/ some payload token filter helpers, such as the NumericPayloadTokenFilter. I was in the process of adding a TokenOffsetPayloadTokenFilter (what a mouthful) that adds the start and end offset as payloads to the token. Now, the easiest way to do this is to encode the first 4 bytes with the startOffset and another 4 bytes as the endOffset. Then it occurs to me that it might make sense to encode them as vInts to save some bits. Naturally, there is no point in duplicating code, so I wonder if it makes sense to make these available for people wanting to encode payloads. Any thoughts on this?

-Grant

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to