[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] [Salvo] Which Store ? Derby or File system
- From: Isuru Udana <isudana@xxxxxxxxx>
- Date: Sun, 12 Jun 2011 00:35:43 +0530
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=N0Foe4llsxb9YKplMykHDapDHXUCp5vDLiSehQDsvrkFma91qUN+sbGsrNp9mWeV7N CiLBKW2MjtZdO/qIulEYj7Cp70EHHFoCJDnQuPH4C/2WUT8htABkbgdbA7TOgz5KnE1D EvkQrjD+OzNe4qDMP5W7PHoGOyQtdHWl/E6os=
On Sun, Jun 12, 2011 at 12:24 AM, Markus Alexander Kuppe <firstname.lastname@example.org>
On 06/11/2011 08:38 PM, Isuru Udana wrote:What kind of data do you intent to store anyway? An SQL db sounds like
> Hi Harshana,
> File System based store implementation uses set of text files to store
> data. For an example "Servers.txt" is used to store server data.
> Derby based store implementation uses apache derby database system.
overkill if you just want to keep a bunch of server configs.
In Salvo we are providing offline reading functionality. So we need to store the retrieved articles.
Salvo is supposed to sync messages to disk, I'd favor something more
sophisticated than a file (e.g. to speed up search).
Would it work to hide storage behind a common API so that storage impl
can be chosen at deployment time?
That hiding is already there.
Derby store and FS store is two implementations of that API.
We need to choose one of them to use for the product.
I think letting user to choose the store system is not user friendly.
ecf-dev mailing list
UndergraduateDepartment of Computer Science & Engineering,
University of Moratuwa.
gTalk: isudana skype: isudana