Hello,
> on user's requirements). A user may choose to upload a file (as
> large as 20
> or 30 megabytes) to the servlet engine. Another user may choose
> to download
> one of these uploaded files. On the backend this is also done
Just a small note on this...
During one project, we had to ma
Hi,
> On the backend this is also done for new mail,
> using Javamail (I might decide to use something else...Javamail is turning
> out to be painfully slow...especially using the Sun JVM.)
What alternatives to Javamail do you see? Whilst we haven't really put it under any
pressure yet, we
Sorry for the late reply everyone...I thought I was resubscribed (my @Home
account was discontinued, and I kept procrastinating about updating my email
addresses)...as it turned out, I missed the request for confirmation I had to
reply to :(
Peter Levart wrote the following excerpt on Feb 13,
On Wednesday 13 February 2002 01:36, you wrote:
> Two things come to mind here. First, values passed over local
> interfaces don't have to be serializable. Second, EJBs are forbidden
> from performing IO, because IO can block forever (you can cheat of
> course). How are you planning on getting t
Are you attempting to put a 20 MB file into a BLOB column in a database
table? If so, I'd suggest you consider just leaving the file in the file
system and putting a reference to it in a small character column. What
benefit are you deriving from putting a file into the database?
- Original
Two things come to mind here. First, values passed over local
interfaces don't have to be serializable. Second, EJBs are forbidden
from performing IO, because IO can block forever (you can cheat of
course). How are you planning on getting this into the database? You
can't create a CMP field
The notion of a serializable stream is not trivial. At first glance, it
suggests that your design may need reconsideration. Can you expand on your
overall requirements and the properties you expect from a serializable
stream?
Paul
> -Original Message-
> From: Daniel Bruce Lynes [mailto
