From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,469b2bba5f3a7bd X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Received: by 10.68.74.201 with SMTP id w9mr1054615pbv.0.1334302549722; Fri, 13 Apr 2012 00:35:49 -0700 (PDT) Path: r9ni50706pbh.0!nntp.google.com!news1.google.com!postnews.google.com!v22g2000vby.googlegroups.com!not-for-mail From: Maciej Sobczak Newsgroups: comp.lang.ada Subject: Re: New AWS-based website Date: Fri, 13 Apr 2012 00:35:49 -0700 (PDT) Organization: http://groups.google.com Message-ID: <27649df6-34b0-4bf5-8d9d-20b86d260639@v22g2000vby.googlegroups.com> References: <76df311e-7bac-4326-bf21-b611c701ebeb@do4g2000vbb.googlegroups.com> <4f868816$0$282$14726298@news.sunsite.dk> <6ea96041-f949-421b-a76e-05ada890ec77@z17g2000yqf.googlegroups.com> <4f86e680$0$294$14726298@news.sunsite.dk> NNTP-Posting-Host: 213.77.7.66 Mime-Version: 1.0 X-Trace: posting.google.com 1334302549 29364 127.0.0.1 (13 Apr 2012 07:35:49 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Fri, 13 Apr 2012 07:35:49 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: v22g2000vby.googlegroups.com; posting-host=213.77.7.66; posting-account=bMuEOQoAAACUUr_ghL3RBIi5neBZ5w_S User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20100101 Firefox/11.0,gzip(gfe) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: 2012-04-13T00:35:49-07:00 List-Id: On 12 Kwi, 16:28, Thomas Locke wrote: > I think it's nice when you have a few dedicated HTML people, who you'd > rather not have mucking around in the Ada code. You can agree on a set > of tags and leave them to work their magic on the GUI side of things. > > At least that's how I've used templating systems in the past (primarily > XSLT based). It's a model I feel works very well. I fully agree with it - if there was such a need, I would divide the work between XML served directly from the server (very likely as a combination of sources as described previously) and the XSLT transformations, which would be under responsibility of other dedicated developers. CSS is on the same side. That's why I see no place for template parsers built into AWS - in other words, between generating HTML directly and generating XML (that is transformed by XSLT on the client side) there is no space left and therefore server-side template parser is a solution to the problem that does not exist. > I've yet to use templates_parser for anything "serious". Exactly. > Ahh yes, the AWS session management system. I too feel that it would be > nice if it were a bit more "flexible", for lack of a better word. I think it does not need to be. Doing it properly (that is, flexibly enough to cover all needs) would be a huge amount of work and it would always be a wrong solution for some purpose. Considering that doing it right in the actual context of the target system is not difficult at all (support for cookies is all that is neededd), there is again no problem to solve with the library-based solution. In other words - if the session management can be done entirely in memory, then a screenful of code does the job and the library has little added value; and if it requires support from the database, then the general-purpose library feature will not be adequate anyway. > AWS Express Edition - that's a pretty darn good idea! What say you > Pascal? =A0:o) :-) -- Maciej Sobczak * http://www.inspirel.com