Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 28526 invoked from network); 26 Jan 2000 06:18:49 -0000 Received: from unknown (HELO host2.altacast.com) (63.84.216.2) by 63.211.145.10 with SMTP; 26 Jan 2000 06:18:49 -0000 Received: from EXCHANGE by host2.altacast.com via smtpd (for [63.211.145.10]) with SMTP; 26 Jan 2000 06:18:49 UT Received: by firewall.altacast.com with Internet Mail Service (5.5.2448.0) id ; Tue, 25 Jan 2000 23:18:49 -0700 Message-ID: <85CDFD92C550D311A1A40008C7DFA81A01D607@firewall.altacast.com> From: "Timm, Sean" Reply-To: cocoon-dev@xml.apache.org To: "'cocoon-dev@xml.apache.org'" Subject: RE: Retrieve the process type within a processor? Date: Tue, 25 Jan 2000 23:18:47 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="windows-1252" It was a momentary lapse of sanity during a brief compromise on design integrity (at least the reason I was looking at it). However, let me explain briefly part of how we are using Cocoon and why I think I might want to do it. We are dynamically generating the cocoon-process tags based on a custom sitemap file (not related to the current Cocoon sitemap proposal) and passing the data off to various processors. It provides a great way to partition functionality so we can add or remove various parts of the system without modifying anything but our sitemap (and cocoon.properties file). In our current design, I don't believe it is necessary, so perhaps this is just a matter of good versus bad design, but it seems you could run into a situation where you are dynamically generating processing tags, and the processor you are currently in determines that it needs data from the user. It passes a page to the user that posts the user's responses back to Cocoon along with information about the processor that needed the data. It queries the site through the sitemap processor which must once again dynamically establish where to pass control off to, and the processor that had to query data is wanting to be called again to complete the processing of the data. The processor that originally decided it needed the data was responsible for querying for that data, so it needs some way to add in the tag information that says "call me again" without having to hard-code the name of the processor specified in the cocoon.properties file. Once again, I don't believe our current design calls for this, but it seems like this could be useful occasionally. Am I once again having a temporary loss of sanity, or does this make some sort of sense? - Sean T. -----Original Message----- From: Stefano Mazzocchi To: cocoon-dev@xml.apache.org Sent: 1/25/00 6:36 AM Subject: Re: Retrieve the process type within a processor? "Timm, Sean" wrote: > > Is there a way (short of parsing the cocoon.properties file) to determine > the process type of the processor you're currently in? > > In other words, > > JoeProcessor is accessed through . > > Is there a way for JoeProcessor (while running) to find out that his short > name is "joe"? It might be possible, but I fail to see a good reason for this. What are you trying to do? -- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. Friedrich Nietzsche -------------------------------------------------------------------- Come to the first official Apache Software Foundation Conference! ------------------------- http://ApacheCon.Com ---------------------