Re: [VuFind-Tech] aleph driver

[Demian K. <dem...@vi...>]

It sounds to me like (as you say) option 3 is the theoretical ideal, but option 2 is perfectly acceptable if you don't have time for all the refactoring - that can always be done in the future if it turns out to be helpful.

Honestly, at this point, I think the most important thing is to get the code shared in some form as quickly as possible - since several people seem to be working on this project in parallel, it would likely save time to get something new into the trunk as soon as we can.  Obviously, if it's not ready, it's not ready...  but I hate to see unnecessary duplication of effort!

- Demian

From: Seaman, Graham [mailto:Gra...@rh...]
Sent: Tuesday, June 14, 2011 6:31 AM
To: vuf...@li...
Subject: [VuFind-Tech] aleph driver

I've been working on our Aleph driver and am wondering what the best direction is to stop it being too hard to merge with others.

We started with a Xserver based implementation.

We then started using the RESTful server, and created an AlephRestful driver extending the base Aleph XServer driver.

Now everything in  our Aleph XServer driver is replicated in the AlephRestful driver. At this point I can see a few options:

-     Rename the AlephRestful driver as Aleph and just use that
-     Carry on having the AlephRestful driver extending the XServer driver, although it overrides most of its functions
-     Create an abstract Aleph base driver, which just has common utility functions, and extend it with separate AlephRestful and AlephXServer drivers

I'd prefer the third in abstract, but am not sure if it's worth the effort.
How do other Aleph users see this going? Will the XServer gradually drop out of use, or do people intend to keep using it?

Graham