Hi - back from Genova - great conference. Anyhow...
If you create a SeqDBLite interface without the troublesome methods, and
have SequenceDB inherit from this and add back the troubling ones, then
I think we are OK. Existing code that purely uses SequenceDB to
fetch-by-index should over time u
[EMAIL PROTECTED]]
> Sent: Tuesday, May 15, 2001 5:19 PM
> To: BioJava List
> Subject: [Biojava-l] sequence dbs
>
>
> I started to work on this at biojava bootcamp, didn't get
> very far because
> of the following:
> seq.db.SequenceDB currently have the following m
the way to go??
>
> Mark
>
> Mark Schreiber
> Bioinformatics
> AgResearch Invermay
> PO Box 50034
> Mosgiel
> New Zealand
>
> PH: +64 3 489 9175
>
>
>
> > -Original Message-
> > From: Jason Stajich [mailto:[EMAIL PROTECTED]]
> > Sent:
eiber
Bioinformatics
AgResearch Invermay
PO Box 50034
Mosgiel
New Zealand
PH: +64 3 489 9175
> -Original Message-
> From: Jason Stajich [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 16, 2001 9:19 AM
> To: BioJava List
> Subject: [Biojava-l] sequence dbs
>
>
>
I started to work on this at biojava bootcamp, didn't get very far because
of the following:
seq.db.SequenceDB currently have the following methods that one cannot
implement for 'remote' databases.
< Set ids();
< SequenceIterator sequenceIterator();
< void addSequence(Sequence seq)
< t
