[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [smila-dev] binstorage redesign
|
Hi,
My 2 cents:
From the perspective of the blackboard we need a binstorage that stores and retrieves a Blob for a given Record ID + Attachment Name. Different implementations of binstorage should optimize this for different applications with respect to data volume and other parameters. Whether it uses a simple shared file system, a distributed file system like Hadoop or even a database should not be relevant to the client (i.e. blackboard). So from this point of view we do not even need the binstorage IDs externally, but could use ID + attachment name in the interface. Additionally we could have a method like
File getAsFile(ID, String)
which gives direct file access to the blob. If it cannot create this File object immediately for the stored data, the service still may have faster possibilities to create the temp file internally than to copy the InputStream.
Of course, we can also design a more generic (i.e. not record/attachment related) interface. But I'm not sure if we already have use cases for such a store. And in this case we will have to store the mapping between record ID + attachment name and binstorage IDs somewhere.
Yours,
Juergen.
> -----Original Message-----
> From: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Ivan Churkin
> Sent: Tuesday, September 30, 2008 10:06 AM
> To: Smila project developer mailing list
> Subject: Re: [smila-dev] binstorage redesign
>
> Yes u r right, I forgot that for VFS user should able to choose folder
> before storing stream))) - so API should be extended.
> But I agree also with Dimitry.
> The question is what we need: binstorage or VFS?
>
