Re: [WebDNA] DNA suffix
This WebDNA talk-list message is from 11:3
It keeps the original formatting.
numero = 100813
interpreted = N
texte = Well, for my 2 cents, I'm new to WebDNA, but I have to agree with Christophe. I have programmed in asp, aspx & php and I like seeing the common extension of the language I coded in if for no other reason to know at a glance what I wrote the site in after not working on it for a couple of years. Additionally, I like knowing what other sites have been written in in the event I think something's "cool" and I want to know how the programmer did it. And finally, the Christophe's point, if you guys are to "resurect" webDNA and have it rise like a pheonix from the ashes (a quote from someone's earlier post), then I think you want as much brand recognition as you can get. I know that when I see a website that @ know is dynamic but is using an extension that I don't recognize, I often look it up to see what it is. And finally, about using .html. I would not recommend that. We all have control over our servers it would appear. However, in a shared hosting environment you often don't. If WebDNA ever gets widely adopted, the hosting companies are not going to map .html to webDNA - just like they don't do it for asp or php. Also, as a programmer, I expect .htm or .html files to be pure html and would think it odd and possibly even incorrect (regardless of whether its possible) to have webdna script in a file designated as html. Anyway, that my 2 cents having been involved with webDNA for the past 5 days. :) ----------------------- Sent from my Treo(r) smartphone -----Original Message----- From: Christophe Billiottet
Date: Wednesday, Sep 17, 2008 10:50 am Subject: Re: [WebDNA] DNA suffix To: Reply-To: Well, this was just that WebDNA, as a web scripting language, is far far behind the others in terms of number of active servers and sites. If you check a php site, there is nothing different between it and any other html site, except for the .php suffix that makes it immediately identifiable: "ah! this is another php site" ;-) PHP too can use any other suffix (just a matter of mapping it) but the default suffix is .php and it seems everybody is satisfied with it. Same with .asp The suffix identifies a technology, and we, WebDNA users, decided to hide our technology. I guess this is not a very good idea if we want to make WebDNA a winner product... chris On Sep 17, 2008, at 12:58, Tom Duke wrote: > Hi, > Have to say that I agree with Dan. > I would certainly support setting .dna as the default suffix - but I like the fact that my sites are not clearly identified with any technology. I also hide the bit with WebDNA comments so there should be no easy way for a user to determine the server side scripting language used. > I would think this would be considered good security practice. > - Tom > --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us old archives: http://dev.webdna.us/TalkListArchive/
Associated Messages, from the most recent to the oldest:
Well, for my 2 cents, I'm new to WebDNA, but I have to agree with Christophe. I have programmed in asp, aspx & php and I like seeing the common extension of the language I coded in if for no other reason to know at a glance what I wrote the site in after not working on it for a couple of years. Additionally, I like knowing what other sites have been written in in the event I think something's "cool" and I want to know how the programmer did it. And finally, the Christophe's point, if you guys are to "resurect" webDNA and have it rise like a pheonix from the ashes (a quote from someone's earlier post), then I think you want as much brand recognition as you can get. I know that when I see a website that @ know is dynamic but is using an extension that I don't recognize, I often look it up to see what it is. And finally, about using .html. I would not recommend that. We all have control over our servers it would appear. However, in a shared hosting environment you often don't. If WebDNA ever gets widely adopted, the hosting companies are not going to map .html to webDNA - just like they don't do it for asp or php. Also, as a programmer, I expect .htm or .html files to be pure html and would think it odd and possibly even incorrect (regardless of whether its possible) to have webdna script in a file designated as html. Anyway, that my 2 cents having been involved with webDNA for the past 5 days. :) ----------------------- Sent from my Treo(r) smartphone -----Original Message----- From: Christophe Billiottet Date: Wednesday, Sep 17, 2008 10:50 am Subject: Re: [WebDNA] DNA suffix To: Reply-To: Well, this was just that WebDNA, as a web scripting language, is far far behind the others in terms of number of active servers and sites. If you check a php site, there is nothing different between it and any other html site, except for the .php suffix that makes it immediately identifiable: "ah! this is another php site" ;-) PHP too can use any other suffix (just a matter of mapping it) but the default suffix is .php and it seems everybody is satisfied with it. Same with .asp The suffix identifies a technology, and we, WebDNA users, decided to hide our technology. I guess this is not a very good idea if we want to make WebDNA a winner product... chris On Sep 17, 2008, at 12:58, Tom Duke wrote: > Hi, > Have to say that I agree with Dan. > I would certainly support setting .dna as the default suffix - but I like the fact that my sites are not clearly identified with any technology. I also hide the bit with WebDNA comments so there should be no easy way for a user to determine the server side scripting language used. > I would think this would be considered good security practice. > - Tom > --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us old archives: http://dev.webdna.us/TalkListArchive/
"JD Ready"
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Multiple prices (1997)
Sendmail & Time Issue (2001)
PIXO (1997)
Question re: FlushDatabases (1997)
Next X hits (1996)
WCS Newbie question (1997)
Help name our technology! (1997)
Need some Java Script Code (2003)
Re[2]: Enhancement Request for WebCatalog-NT (1996)
RE: WebCat name recognition (was MacFinder -- a new WebDNAweb site) (1998)
Quit revisited (1997)
email bounce check (2002)
OT - How to pay commissions to non US affiliates? (2000)
iTools/WebDNA Email (2005)
[WebDNA] Friday's.. WIP thread (2009)
WebCat2 Append problem (B14Macacgi) (1997)
PCS Frames (1997)
[WebDNA] Secure Cookies (2020)
Looking up two prices in database? (1997)
Looking for a special Image Upload Script (2004)