It's been a long time since I last looked inside Artemis (pre the Swing version), so I'm trying to refresh my memory.
Say I had an hhtp server which could send out bits of sequence/annotation for clients doing a GET and receieve updates when they did a POST. If I wanted Artemis to be such a client, am I right in thinking I would need to create just these: SomeSortOfEntrySource implements EntrySource SomeSortOfEntry implements Entry SomeSortOfFeature implements Feature SomeSortOfSequence implements Sequence If I model this on the CORBA system I can make a RWSomeSortOfFeature analagous to a RWCorbaFeature. This would implement VersionedFeature instead of DateStampFeature, but with the same purpose - optimistic locking. Does this sound reasonably sane? You can see where I'm going with this... I'll probably want to take a complex gene structure and flatten into generic features, then build it back up again later. That would mean keeping parent/child tags as qualifiers. Presumably it's up to the RWSomeSortOfFeature to stop people deleting these? Has anyone requested the ability to make some qualifiers invisible to the in the viewer/editor? cheers, Keith -- - Keith James <[EMAIL PROTECTED]> Microarray Facility, Team 65 - - The Wellcome Trust Sanger Institute, Hinxton, Cambridge, UK -
