AW: FOP in production app (clienside)

2003-03-12 Thread Müller, Markus
Hi,

You have to consider the additional JARs used by FOP (Xalan, Avalon, ...).
IMHO you get somewhat around 5 MB of JARs. It will take a long time for your
users to download so much stuff (at least the first time they use the
applet). This was the reason for us to have FOP on the server and send PDF
from there to the client.

Markus

$ -Ursprüngliche Nachricht-
$ Von: Van Camp, Kenneth (Exchange) [mailto:[EMAIL PROTECTED] 
$ Gesendet: Mittwoch, 12. März 2003 14:56
$ An: '[EMAIL PROTECTED]'
$ Betreff: RE: FOP in production app
$ 
$ 
$ I saw a number of posted responses to David's query but it 
$ seems like most
$ respondents are using FOP on the server side.  Is there much 
$ experience in
$ using FOP on the client side, say inside of an applet?  I am 
$ interested in
$ streaming XSLT to the user's browser and having an applet 
$ transform it into
$ a PDF, then invoke Acrobat reader to render it on the desktop.
$ 
$ Is this a common application?  It is related to this thread 
$ in that I am
$ concerned about production support in such an environment.
$ 
$ Is there a better way?  Thanks.
$ 
$ Ken Van Camp [EMAIL PROTECTED]
$ 
$ -Original Message-
$ From: Holk, David A [mailto:[EMAIL PROTECTED] 
$ Sent: Monday, March 10, 2003 12:37 PM
$ To: '[EMAIL PROTECTED]'
$ Subject: FOP in production app
$ 
$ 
$ Is anyone using FOP in a production app? 
$ 
$ Should I expect a commercial product like XEP or 
$ XSLFormatter to be more
$ robust in a production application?
$ 
$ Any experiences/comments appreciated.
$ 
$ David Holk
$ 
$ 
$ LEGAL NOTICE
$ Unless expressly stated otherwise, this message is 
$ confidential and may be
$ privileged. It is intended for the addressee(s) only. Access 
$ to this E-mail
$ by anyone else is unauthorized. If you are not an addressee, 
$ any disclosure
$ or copying of the contents of this E-mail or any action 
$ taken (or not taken)
$ in reliance on it is unauthorized and may be unlawful. If 
$ you are not an
$ addressee, please inform the sender immediately.
$ 
$ -
$ To unsubscribe, e-mail: [EMAIL PROTECTED]
$ For additional commands, e-mail: [EMAIL PROTECTED]
$ 
$ 
$ *
$ **
$ Bear Stearns is not responsible for any recommendation, 
$ solicitation, 
$ offer or agreement or any information about any transaction, 
$ customer 
$ account or account activity contained in this communication.
$ *
$ **
$ 
$ 
$ -
$ To unsubscribe, e-mail: [EMAIL PROTECTED]
$ For additional commands, e-mail: [EMAIL PROTECTED]
$ 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



AW: FOP in production app (clienside)

2003-03-12 Thread s-oualid
I agree with Markus. 

FOP needs so much JARs and rendering PDF take so much ressources that I 
think it's better to do the transformations server side and then send the 
result to the client. That is my opinion about using FOP clientside with 
an applet (for web app, I think the servlet approach is better). But I 
already used command line version of FOP (clientside) integrated in my VB 
app using SHELL32.DLL, it is working well, we just had to deploy the 
proper JAR's over the network.

Cheers,

Simon

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: FOP in production app (clienside)

2003-03-12 Thread Van Camp, Kenneth (Exchange)

Good point.

Here's my problem: I need to generate on-demand some good-size PDFs (a few
hundred pages) for a lot of users.  Our tests with FOP indicate it is too
resource intensive to do on my web servers for this many users, so I'd like
to generate XSLT and somehow let the client's PC do the transform to PDF.

If applet is not practical, I wonder if there are any browser plug-ins that
can do it (hopefully much smaller than 5MB)?  It would be great if Adobe
produced a version of Acrobat that can consume XSLT and render the PDF
directly, but I have not heard anything to indicate they are working on
this.

-Original Message-
From: Müller, Markus [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 12, 2003 9:18 AM
To: [EMAIL PROTECTED]
Subject: AW: FOP in production app (clienside)


Hi,

You have to consider the additional JARs used by FOP (Xalan, Avalon, ...).
IMHO you get somewhat around 5 MB of JARs. It will take a long time for your
users to download so much stuff (at least the first time they use the
applet). This was the reason for us to have FOP on the server and send PDF
from there to the client.

Markus

$ -Ursprüngliche Nachricht-
$ Von: Van Camp, Kenneth (Exchange) [mailto:[EMAIL PROTECTED] 
$ Gesendet: Mittwoch, 12. März 2003 14:56
$ An: '[EMAIL PROTECTED]'
$ Betreff: RE: FOP in production app
$ 
$ 
$ I saw a number of posted responses to David's query but it 
$ seems like most
$ respondents are using FOP on the server side.  Is there much 
$ experience in
$ using FOP on the client side, say inside of an applet?  I am 
$ interested in
$ streaming XSLT to the user's browser and having an applet 
$ transform it into
$ a PDF, then invoke Acrobat reader to render it on the desktop.
$ 
$ Is this a common application?  It is related to this thread 
$ in that I am
$ concerned about production support in such an environment.
$ 
$ Is there a better way?  Thanks.
$ 
$ Ken Van Camp [EMAIL PROTECTED]
$ 
$ -Original Message-
$ From: Holk, David A [mailto:[EMAIL PROTECTED] 
$ Sent: Monday, March 10, 2003 12:37 PM
$ To: '[EMAIL PROTECTED]'
$ Subject: FOP in production app
$ 
$ 
$ Is anyone using FOP in a production app? 
$ 
$ Should I expect a commercial product like XEP or 
$ XSLFormatter to be more
$ robust in a production application?
$ 
$ Any experiences/comments appreciated.
$ 
$ David Holk


***
Bear Stearns is not responsible for any recommendation, solicitation,
offer or agreement or any information about any transaction, customer
account or account activity contained in this communication.
***


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: FOP in production app (clienside)

2003-03-12 Thread Oleg Tkachenko
Van Camp, Kenneth (Exchange) wrote:
If applet is not practical, I wonder if there are any browser plug-ins that
can do it (hopefully much smaller than 5MB)? 
I'd look to Java Web Start. 5MB is required, but it can be downloaded once only.
 It would be great if Adobe
produced a version of Acrobat that can consume XSLT and render the PDF
directly, but I have not heard anything to indicate they are working on
this.
They are working on server side, which costs 20K actually.
--
Oleg Tkachenko
Multiconn Technologies, Israel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: FOP in production app (clienside)

2003-03-12 Thread Philip Semanchuk
On Wed, 2003-03-12 at 11:03, Van Camp, Kenneth (Exchange) wrote:
 If applet is not practical, I wonder if there are any browser plug-ins that
 can do it (hopefully much smaller than 5MB)?  It would be great if Adobe
 produced a version of Acrobat that can consume XSLT and render the PDF
 directly, but I have not heard anything to indicate they are working on
 this.

Rendering XSL FO -- PDF is a pretty complex task and I would be
surprised if you find any simple applications to do it. By simple I
mean apps that don't require that you have already installed a parser,
etc. 

Adobe Document Server
(http://www.adobe.com/products/server/documentserver/main.html) lists
among its key features that it can Flow XML data into templates using
standard XSL-FO formatting. This is only one of eleven key features so
one can hardly say it is the main focus of the product but it seems like
Adobe is paying some attention to rendering XSL FO. But this, like FOP,
is a product intended for server-side use and for much the same reasons
I suspect.

Good luck
Philip


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: FOP in production app (clienside)

2003-03-12 Thread s-oualid
We had the same needs, generate on-demand big PDF with some images 
(between 200 and 500 pages), fop is mostly used here by the employees in 
their usual apps, but there was also a few need for our websites' users.

We first have integrated FOP in our front apps using SHELL32.DLL in Visual 
Basic environment. So we just had to deploy the JARs over the network and 
the renders were made by the clients. Then we made a servlet to integrate 
our work on the websites.

If your clients are on a Windows platform, why don't you use a customised 
command line version of FOP which could be easily integrated into your 
client app ? 

As I said, we did that here, a command line version for the (lots of) 
client users here in the society, and a servlet embedded version for the 
(few) remote users.

Simon





Van Camp, Kenneth (Exchange) [EMAIL PROTECTED]
12/03/2003 17:03
Veuillez répondre à fop-user

 
Pour :  '[EMAIL PROTECTED]' [EMAIL PROTECTED]
cc : 
Objet : RE: FOP in production app (clienside)



Good point.

Here's my problem: I need to generate on-demand some good-size PDFs (a few
hundred pages) for a lot of users.  Our tests with FOP indicate it is too
resource intensive to do on my web servers for this many users, so I'd 
like
to generate XSLT and somehow let the client's PC do the transform to PDF.

If applet is not practical, I wonder if there are any browser plug-ins 
that
can do it (hopefully much smaller than 5MB)?  It would be great if Adobe
produced a version of Acrobat that can consume XSLT and render the PDF
directly, but I have not heard anything to indicate they are working on
this.






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: FOP in production app (clienside)

2003-03-12 Thread Patrick Dean Rusk
I use Java Web Start to deliver a Java application embedding FOP and it
works great.  I consider a one-time 5M download to be small these days,
compared to lots of other internet practices people frequently use (like
downloading game demos).  Besides, you can quickly surpass 5M in PDF
downloads by clients generating PDF files server-side, particularly if
you're using any SVG.

Rendering large FOP documents server-side (or client-side) is very
resource-intensive, and it doesn't take much math to figure out that you
will quickly need to have a number of servers to support any significant
population of active users.  For my purposes, the incremental cost
associated with adding a new user under a server-side arrangement would
exceed what I could charge them.

Meanwhile, their CPUs would be sitting 99% idle waiting for the document to
render on the server

Patrick Rusk


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]