> > Would a .NET port be worthwhile? Very much so. > > Is there a reason the .NET app can't communicate with FOP > over a network connection ? Why is a port needed ? >
It's not needed, but it would be nice to be able to make homogeneous solutions, and there may be a significant performance gain using a native bindning. > > They just might do that, and while they're at it, they'll probably launch an > > alternative to PDF... > > Not enough money in it relative to the anti-trust headache > Probably true. > > PS. Currently I'm using FOP from .NET using a Web Service wrapper, which > > works just fine, although there is some overhead in this solution. DS > > But it works and resource use will go down soon. > Good news! /G --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
