Hi Studs,
thanks a lot for taking so much interest in my
question.Am really overwhelmed by your responses. Please gimme some time to
do my homework too( i need to know how much processing we need to do on the
image,how long should we persist with the image, use client-side browser
cache (as somebody pointed out) or go for Corba soln.) I need sometime to
weigh my options and give you details of what we are finally doing( whetehr
using EJB at all!).
Thanks once again, :-)
Aashish
P.S: If anyone on the list doesnt want to recieve mails on this discussion,
please do inform me, we will localize the discussion.
--------------------------------------------------------------------
Aashish:
We have a similar product where we need to serve lot of images. In the
current product we used CORBA to create an ImageServer and pass the Image to
the Client as a ByteStream. However, when tried to port the logic to EJB, I
did not have much success, as ByteStreams do not implement Serializable.
If you want to process huge data transfers, my suggestion is to use Servlet
(provided u you trying to serve the images to the Web Tier) and access the
database. If you want scalability you can go for the CORBA solution.
Currently, it works well for us. You can use the Servlet OutputStream and
write the image to the outputstream and set the correct mime type. This can
be served straight to the browser. IMHO as some ppl have pointed out, not
everthing might be a good fit for EJBs.
I am open to any other suggestion(s) from other members of the group as
well.
Thanks.
-Sunil Kuchipudi
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".