Return-Path: X-Original-To: apmail-commons-user-archive@www.apache.org Delivered-To: apmail-commons-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D6AA84077 for ; Mon, 6 Jun 2011 21:36:17 +0000 (UTC) Received: (qmail 44511 invoked by uid 500); 6 Jun 2011 21:36:16 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 44420 invoked by uid 500); 6 Jun 2011 21:36:16 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 44412 invoked by uid 99); 6 Jun 2011 21:36:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Jun 2011 21:36:16 +0000 X-ASF-Spam-Status: No, hits=3.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of darac1111@gmail.com designates 74.125.82.171 as permitted sender) Received: from [74.125.82.171] (HELO mail-wy0-f171.google.com) (74.125.82.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Jun 2011 21:36:10 +0000 Received: by wyb32 with SMTP id 32so3550071wyb.30 for ; Mon, 06 Jun 2011 14:35:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=ZUomd/LsY8ImrJD8X4zhrXSyeQXsMJQne4/RU8IYnVA=; b=C2LsGM79URjcaTzh5EEU2F363ZhNazEHcZ7Oz33OpHPXgtYgzLJz96skhYKYMMOLRn kiaq6Yx+4lXG2uh6NgbG5Oo+Ch0vfLiDX47I7E2Wo//wRSXZf+SxFdAETLrV0PfIDhQ+ jt/Ka1Oa2Tc8R9kbud+8IM9UcAX75Nlu11HjY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=uzAjyfPmlqeGS+xw+o15ppr4g4K+Roo9uc2Qpa8vEIQ+3/wpvePckF3531RONex8jj cMGZz5eqG9xy7k6dZH3EISsL3pnR0LTshpHTUcxvq6jfFB5uaEXrkMdHkzY7td7xtv7i VUYo99VNGJknzqJqPxmOEYi3nWJ4ZTvdu8JHo= MIME-Version: 1.0 Received: by 10.227.12.18 with SMTP id v18mr5434625wbv.89.1307396148720; Mon, 06 Jun 2011 14:35:48 -0700 (PDT) Received: by 10.227.37.158 with HTTP; Mon, 6 Jun 2011 14:35:48 -0700 (PDT) Date: Mon, 6 Jun 2011 23:35:48 +0200 Message-ID: Subject: [scxml] src element as a pointer to memory content From: Dario D To: user@commons.apache.org Content-Type: multipart/alternative; boundary=002215975fe206739204a511e35e --002215975fe206739204a511e35e Content-Type: text/plain; charset=ISO-8859-1 Hello, Would it be possible to have a PathResolver implementation which treats the "src" element as a pointer to a database entry where content is stored, or an in-memory object? Of course, I could make a PathResolver implementation which will parse the value of "src" make a query to the database, download the content to a file, and then return file path as the result of the resolvePath() method. However, I would like to skip the step of making a file on the disk just for the purpose of loading the "src" content. Ideally, this PathResolver implementation would be able to read content directly from a memory object (perhaps a cache of some sort), without the need of creating a file. I'm planning to use SCXML in a high-throughtput environment and I feel that writing files on the disk and then reading them back will slow the process down a bit. One of the requirements for the application is to be able to split SCXML files into many reusable modules, thus the need to use the "src" element. Any thoughts? --002215975fe206739204a511e35e--