[Jdbm-developer] RE: jdbm.helper.StringSerializer;

Alex,
Thanks for pointing this out. I have added the class to CVS. As I
mentioned, I have several changes that I have made but not committed
dealing with the extensible serialization mechanism. I had not realized
that the StringTable depended on one of the new serializers that I
had introduced.
With respect to the strings package itself, there are alternative
approaches and a metrics-based exploration of them could be worth
while. I just did the simplest thing, which uses one btree to
lookup by string value and another to lookup by string index.
I've also created a separate entry for jdbm in eclipse so that I can
get the current cvs state and make sure that it all compiles in the
future. (I had to do this using the IP address of cvs.sourceforge.net
since eclipse otherwise detects this as a duplicate repository entry.)
I found that I had one other unresolved reference in
LeadingValueCompressionProvider, which I also committed.
Everything should be fine now.
Cheers,
-bryan
-----Original Message-----
From: Alex Boisvert
To: Thompson, Bryan B.
Sent: 10/7/2005 9:09 PM
Subject: jdbm.helper.StringSerializer;
Bryan,
We appear to be missing class jdbm.helper.StringSerializer in CVS; it
is used by jdbm.strings.StringTable.
Could you look into this?
thanks,
alex

Thread view

Alex,
Thanks for pointing this out. I have added the class to CVS. As I
mentioned, I have several changes that I have made but not committed
dealing with the extensible serialization mechanism. I had not realized
that the StringTable depended on one of the new serializers that I
had introduced.
With respect to the strings package itself, there are alternative
approaches and a metrics-based exploration of them could be worth
while. I just did the simplest thing, which uses one btree to
lookup by string value and another to lookup by string index.
I've also created a separate entry for jdbm in eclipse so that I can
get the current cvs state and make sure that it all compiles in the
future. (I had to do this using the IP address of cvs.sourceforge.net
since eclipse otherwise detects this as a duplicate repository entry.)
I found that I had one other unresolved reference in
LeadingValueCompressionProvider, which I also committed.
Everything should be fine now.
Cheers,
-bryan
-----Original Message-----
From: Alex Boisvert
To: Thompson, Bryan B.
Sent: 10/7/2005 9:09 PM
Subject: jdbm.helper.StringSerializer;
Bryan,
We appear to be missing class jdbm.helper.StringSerializer in CVS; it
is used by jdbm.strings.StringTable.
Could you look into this?
thanks,
alex

Sounds great.
-bryan
-----Original Message-----
From: Alex Boisvert
To: Thompson, Bryan B.
Cc: 'jdbm-developer@...'
Sent: 10/8/2005 12:04 PM
Subject: Re: jdbm.helper.StringSerializer;
Bryan, thanks for taking care of all this.
Regarding the new serialization framework proposal you've made, I don't
have any objections myself.
At this point, I'd like to see Kevin a more elaborate view of his own
solution since he appeared to have different views.
After that, we could assess/debate the relative merits of both
approaches and move on to bigger things.
alex
Thompson, Bryan B. wrote:
> Alex,
>
> Thanks for pointing this out. I have added the class to CVS. As I
> mentioned, I have several changes that I have made but not committed
> dealing with the extensible serialization mechanism. I had not
realized
> that the StringTable depended on one of the new serializers that I
> had introduced.
>
> With respect to the strings package itself, there are alternative
> approaches and a metrics-based exploration of them could be worth
> while. I just did the simplest thing, which uses one btree to
> lookup by string value and another to lookup by string index.
>
> I've also created a separate entry for jdbm in eclipse so that I can
> get the current cvs state and make sure that it all compiles in the
> future. (I had to do this using the IP address of cvs.sourceforge.net
> since eclipse otherwise detects this as a duplicate repository entry.)
> I found that I had one other unresolved reference in
> LeadingValueCompressionProvider, which I also committed.
>
> Everything should be fine now.
>
> Cheers,
>
> -bryan
>
> -----Original Message-----
> From: Alex Boisvert
> To: Thompson, Bryan B.
> Sent: 10/7/2005 9:09 PM
> Subject: jdbm.helper.StringSerializer;
>
>
> Bryan,
>
> We appear to be missing class jdbm.helper.StringSerializer in CVS; it
> is used by jdbm.strings.StringTable.
>
> Could you look into this?
>
> thanks,
> alex
--
Alex Boisvert, Product Development Director
Intalio, Inc. | http://www.intalio.com
boisvert@...

Bryan, thanks for taking care of all this.
Regarding the new serialization framework proposal you've made, I don't
have any objections myself.
At this point, I'd like to see Kevin a more elaborate view of his own
solution since he appeared to have different views.
After that, we could assess/debate the relative merits of both
approaches and move on to bigger things.
alex
Thompson, Bryan B. wrote:
> Alex,
>
> Thanks for pointing this out. I have added the class to CVS. As I
> mentioned, I have several changes that I have made but not committed
> dealing with the extensible serialization mechanism. I had not realized
> that the StringTable depended on one of the new serializers that I
> had introduced.
>
> With respect to the strings package itself, there are alternative
> approaches and a metrics-based exploration of them could be worth
> while. I just did the simplest thing, which uses one btree to
> lookup by string value and another to lookup by string index.
>
> I've also created a separate entry for jdbm in eclipse so that I can
> get the current cvs state and make sure that it all compiles in the
> future. (I had to do this using the IP address of cvs.sourceforge.net
> since eclipse otherwise detects this as a duplicate repository entry.)
> I found that I had one other unresolved reference in
> LeadingValueCompressionProvider, which I also committed.
>
> Everything should be fine now.
>
> Cheers,
>
> -bryan
>
> -----Original Message-----
> From: Alex Boisvert
> To: Thompson, Bryan B.
> Sent: 10/7/2005 9:09 PM
> Subject: jdbm.helper.StringSerializer;
>
>
> Bryan,
>
> We appear to be missing class jdbm.helper.StringSerializer in CVS; it
> is used by jdbm.strings.StringTable.
>
> Could you look into this?
>
> thanks,
> alex
--
Alex Boisvert, Product Development Director
Intalio, Inc. | http://www.intalio.com
boisvert@...