[dev] [cvs] commit: dimp/js DimpBase.js ViewPort.js dimp/js/src DimpBase.js ViewPort.js

[Michael M Slusarz]

Quoting Chuck Hagenbuch <chuck at horde.org>:

> Quoting Michael M Slusarz <slusarz at horde.org>:
>
>>   Log:
>>   New, more powerful search interface, based in part on the search interface
>>   used by Taffy DB (http://taffydb.com/). Allows us to better
>> identify and string
>>   queries, and will allow easily extensibility in case we need
>> additional query
>>   filters in the future. Add a 'not' search that will be used in
>> some new code
>>   I am currently still testing.
>
> Sounds pretty cool - do you think this is applicable to other apps
> also perhaps?

Possibly.  Pros are it is released on a BSD license, and appears to be  
a very thorough DB, albeit one with a very managable API and is fairly  
small when compressed (< 10 KB).  Cons are that the code is pretty  
hard to follow/read (although if we are simply including like  
prototype, that is not a big deal) and that it might be overkill for  
stuff that we do.

I could see us using this in the future as something to use when first  
developing an application, but as the application matures it is  
probably best to look at coding our own solution.  i.e. in DIMP the  
custom-built DB we are using for cached mailbox info is optimized for  
its purpose (we have optimized row/uid lookup tables rather than doing  
a search for such data for example), and our search needs are  
extremely limited so there is not much need for 80+% of the search  
options provided by the API.  Although it might be interesting to see  
if the code could be extended to do something such as auto-indexing by  
various keys - this might make it usable in the future.  Additionally,  
the next generation of browsers (FF3, apparently the new  
"squirrelfish" JS engine for webkit) is going to have much faster JS  
implementations, so optimizing at the expense of a standard  
browser-side DB solution might become less important.

michael

-- 
___________________________________
Michael Slusarz [slusarz at horde.org]