From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Joe Brenner Newsgroups: gmane.emacs.help Subject: Re: Multiple Major Modes Date: Fri, 11 Dec 2009 18:37:58 -0800 Message-ID: <200912120238.nBC2bw3e070726@kzsu.stanford.edu> References: <25d42153-4e90-4491-b0a0-7efff5215f35@k17g2000yqh.googlegroups.com> <87fx918sr7.fsf@kzsu.stanford.edu> <87ljhaav81.fsf@kzsu.stanford.edu> <200912112158.nBBLvxHp067219@kzsu.stanford.edu> <200912120216.nBC2GT1V070435@kzsu.stanford.edu> NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1260585528 13002 80.91.229.12 (12 Dec 2009 02:38:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 12 Dec 2009 02:38:48 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: Lennart Borgman Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Dec 12 03:38:41 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NJHsW-0007Vw-PN for geh-help-gnu-emacs@m.gmane.org; Sat, 12 Dec 2009 03:38:41 +0100 Original-Received: from localhost ([127.0.0.1]:51974 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NJHsW-000417-1B for geh-help-gnu-emacs@m.gmane.org; Fri, 11 Dec 2009 21:38:40 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NJHs3-0003z9-7H for help-gnu-emacs@gnu.org; Fri, 11 Dec 2009 21:38:11 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NJHry-0003uI-Oy for help-gnu-emacs@gnu.org; Fri, 11 Dec 2009 21:38:10 -0500 Original-Received: from [199.232.76.173] (port=43914 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NJHry-0003u8-F2 for help-gnu-emacs@gnu.org; Fri, 11 Dec 2009 21:38:06 -0500 Original-Received: from smtp5.stanford.edu ([171.67.219.85]:55674 helo=smtp.stanford.edu) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NJHry-0000pm-4T for help-gnu-emacs@gnu.org; Fri, 11 Dec 2009 21:38:06 -0500 Original-Received: from smtp.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 6047018F911; Fri, 11 Dec 2009 18:38:04 -0800 (PST) Original-Received: from kzsu.stanford.edu (KZSU.Stanford.EDU [171.66.118.90]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.stanford.edu (Postfix) with ESMTPS id 1601618F900; Fri, 11 Dec 2009 18:38:04 -0800 (PST) Original-Received: from kzsu.stanford.edu (localhost.stanford.edu [127.0.0.1]) by kzsu.stanford.edu (8.13.4/8.13.7) with ESMTP id nBC2bw3e070726; Fri, 11 Dec 2009 18:38:03 -0800 (PST) (envelope-from doom@kzsu.stanford.edu) In-reply-to: Comments: In-reply-to Lennart Borgman message dated "Sat, 12 Dec 2009 03:18:44 +0100." X-Mailer: MH-E 8.1; nmh 1.2; GNU Emacs 23.1.50 X-Scanned-By: MIMEDefang 2.56 on 171.66.118.47 X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-2.0.2 (kzsu.stanford.edu [127.0.0.1]); Fri, 11 Dec 2009 18:38:03 -0800 (PST) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:70614 Archived-At: Lennart Borgman wrote: > Joe Brenner wrote: > > Lennart Borgman wrote: > >> >> >> to test it. (BTW, what file extensions do Mason files normally have?) > >> >> > > >> >> > The currently recommended Mason file extensions are *.mhtml for internal > >> >> > components, and *.html for external ones: > >> >> > > >> >> > http://www.masonhq.com/?FAQ:ServerConfiguration#h-what_filename_extensions_should_i_use_for_mason_components_ > >> >> > > >> >> > That means, of course that the file extension alone gives you no way to > >> >> > distinguish between a plain html file and a top-level Mason file. > >> >> > >> >> Thanks. I am a bit surprised by the second convention. > >> > > >> > The reasoning seems to be that the client is asking for html, and that's > >> > what you're going to deliver to them... the fact that Mason is used to > >> > generate the html is an internal detail there's no point in bothering > >> > them with. > >> > >> Hm, I see. It is maybe a pretty good reason on that side. But do > >> clients really care about the URL "file extension"? > > > > Well, I do. If the URL ends in ".asp", I think "oh, no...". > Oh, you are not the type of client I was thinking of... I am glad to > hear you care though ;-) > > I was more thinking about web browsers. No, not web browsers, exactly. But a common use case for Mason is re-engineering sites that were developed statically and turned out to be maintenance nightmares. There the published interface is URLs ending in *.html, and changing that because you're changing the back-end wouldn't make any sense.