"Yonik Seeley" <[EMAIL PROTECTED]> wrote:
> So I think we should change + finalize the payload API before Lucene
> 2.3 comes out.
> 
> Single biggest drawback about current payloads is that there isn't any
> explicit support for adding different types of payloads to the same
> token.
> I don't really see a good fix to that though, so I'm OK with leaving
> that as it is.
> 
> One change I'd support is to remove the Payload class and replace it
> with members directly on Token:
> 
> class Token {
>     byte[] payload;
>     int payloadLength;
>     void setPayload(byte[], int length)
>     byte[] getPayload()
>     int getPayloadLength()
> ...
> }

+1

Mike

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

Reply via email to