Hi Christophe,
thanks for your fast response!
> Thanks for providing all this information, it helps me understand
> your system a little better. It looks like you are storing all
> document content in the database and I beleive that most of the
> load comes from this.
Yep.
> Do you have any idea of the size of Blobs you are dealing with?
Actually the size of each BLOBs is not that big (50 KB until 10 MB).
But we use many BLOBs. That's the problem ;-)
> I am not an expert at this kind of load issues, but for having
> been involved in designing document managment systems, I am a
> little surprised with your approach. When managing hundred of
> documents the usual approach is not to store documents in the
> database but just to index them. As you can imagine, just
> streaming the document content over a servlet is way lighter
> than converting that to a Blob. Am I missing something?
Do you mean, you just save the documents in the file system?
Like this?
- For downloading a file:
servlet --> get index from EJB --> get the file from the
file system --> give this back to the servlet -->
send it back to the client.
What I did is like this:
- For showing a list of files:
servlet --> get all files (without the content) from
EJB --> give this back to the servlet --> show to the client
- For downloading a file:
servlet --> get the file from EJB --> give this file back to
the servlet --> send it back to the client.
There are some benefits of saving the documents in the database:
- The create, delete, update operations you do
with these docs are safely transacted. Imagine
if one method does some create, delete, update and
other operations and at the end depending on the result
of those operations the file should be created (commit)
or not (rollback).
If you put your docs in the file system, you have to take
care of this by yourself. You cannot let your docs
"working" within a transaction. With EJBs and saving the docs
in the database this can be done easily.
And of course disadvantages:
- The DB has to have the capability to handle this.
As you wrote: "streaming the document content over a servlet
is way lighter" and this is true ;-)
I think EJB server has to have the capability to handle
this...
I already implemented the same system (with saving
the docs in the database) using DCOM as the middleware
and it worked very well and stable ;-)
Thanks a lot!
--
---------------------------------------------------
Blasius Lofi Dewanto
---------------------------------------------------
OpenUSS - Open University Support System
http://openuss.sourceforge.net
---------------------------------------------------
E-Mail : [EMAIL PROTECTED]
ICQ : 39343280
---------------------------------------------------
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
