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 1246 invoked from network); 27 Oct 2000 03:50:13 -0000 Received: from kcmso1.att.com (HELO kcmso1.proxy.att.com) (192.128.133.69) by locus.apache.org with SMTP; 27 Oct 2000 03:50:13 -0000 Received: from attrh2.attrh.att.com ([135.38.12.15]) by kcmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id XAA05506 for ; Thu, 26 Oct 2000 23:49:47 -0400 (EDT) Received: from puma.mt.att.com by attrh2.attrh.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id XAA11767 for ; Thu, 26 Oct 2000 23:48:43 -0400 (EDT) Received: from localhost by puma.mt.att.com (SMI-8.6/SMI-SVR4) id XAA06343; Thu, 26 Oct 2000 23:43:54 -0400 Date: Thu, 26 Oct 2000 23:43:54 -0400 (EDT) From: I-Chung Young Sender: ichung@puma.mt.att.com To: cocoon-users@xml.apache.org Subject: How to do this or it is the wrong way to go Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N All, I am struggle with how to integrate Cocoon with Phone.com's Digest content type (multipart/mixed). The (raw) output (http response) should be something like: ----------- start here ---------- Content-type: multipart/mixed; boundary="abcd" __abcd Content-type: application/x-up-cacheop ..... __abcd Content-type: text/vnd.wap.wml .... __abcd-- ----------- end here ---------- One fundamental question, should I even bother to solve this problem using cocoon? I know I can use servlet to include result of wml (which is the result of XSP page). However, the link in xsp page is not generic for all (HTML/WML) I cannot setup digest as a new formatter. I got error on output text before element with XML formatter. Or all wml tag is striped off with text formatter. I even consider using/modifying DB Prism's HeaderProcessor and use it in XML. But this should only apply to WML pages. Where does this kind of device dependent control belong to content or presentation or management (as in Cocoon2)? Or shouldn't be mixed with publishing framework. Any suggestion? Thanks. ------------ I-Chung Young ichung@puma.mt.att.com