Return-Path: Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 13260 invoked from network); 9 Jul 2000 12:51:03 -0000 Received: from frankfurt.denic.de (HELO notes.denic.de) (194.246.96.101) by locus.apache.org with SMTP; 9 Jul 2000 12:51:03 -0000 Received: from denics7 ([192.168.0.63]) by notes.denic.de (Lotus Domino Version 5.0.2c (Intl)) with ESMTP id 2000070914500614:1360 ; Sun, 9 Jul 2000 14:50:06 +0200 Date: Sun, 9 Jul 2000 14:50:07 +0200 (MET DST) From: Uli Mayring To: cocoon-users@xml.apache.org Subject: RE: To contrib or not to contrib In-Reply-To: Message-ID: "X-Ncc-RegID: de.denic" MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on notes/Denic(Version 5.0.2c (Intl)|08 Februar 2000) at 09.07.2000 14:50:06, Serialize by Router on notes/Denic(Version 5.0.2c (Intl)|08 Februar 2000) at 09.07.2000 14:50:18, Serialize complete at 09.07.2000 14:50:18 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 9 Jul 2000, Torsten Curdt wrote: > What about the DOM includes from the SQL processor? This should not > be not at issue to this barrier because it's just a DOM addition, > right?! (Please tell me that I'm right!) You are right. The output of the SQL and XInclude processor is not compiled, it is just added to the DOM tree. I don't know what happens if you use the SQL taglib, though. Perhaps it has the same problem, I don't know how it is implemented. But the SQL processor is safe, I tested it with pretty large result sets from the db. > > It was suggested to me that the 64K barrier could be changed via an > > undocumented command-line option to the JVM. For sure, I have not found a > > single byte of documentation about this limit anywhere. > > If not this would be a serious misconception and will get into big trouble > since I voted for Cocoon! :-| Well, if you don't use XSP in your large XML files, then you're ok. Ulrich -- Ulrich Mayring DENIC eG, Softwareentwicklung