Re: [WebDNA] DNA suffix

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 100829
interpreted = N
texte = This is a multipart message in MIME format. ------=_NextPart_000_0001_3711BCAF.2A9F77AE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I agree with all that was said, EXCEPT... I certainly don't want to lose my Google Page Rank and SEO just because the software platform wants to change extensions. I would gladly code new sites using .dna, but the existing ones need to stay as .tpl. Best Regards, Chris Whybrew Senior Account Manager PLANET DJ INC www.planetdj.com p: 775.323.1540 ext 3903 f: 775.323.8230 e: chrisw@planetdj.com ---------------------------------------- From: "JD Ready" Sent: Wednesday, September 17, 2008 10:32 AM To: talk@webdna.us Subject: Re: [WebDNA] DNA suffix 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/ --------------------------------------------------------- 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/ ------=_NextPart_000_0001_3711BCAF.2A9F77AE Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I agree with all that was said, EXCEPT... I certainly don't want t= o lose my Google Page Rank and SEO just because the software platform wants= to change extensions. I would gladly code new sites using .dna, but the ex= isting ones need to stay as .tpl.

Best Regards,

Chris= Whybrew
Senior Account Manager


PLANET= DJ INC
= www.planetdj.com

= p: 775.323.1540 ext 3903
f: 775.323= .8230
e:
<= FONT face=3DVerdana color=3D#497699>chrisw@planetdj.com




From: "JD Ready" <jdready@risedev.com>
Sent: Wednesd= ay, September 17, 2008 10:32 AM
To: talk@webdna.us
Subject<= /B>: Re: [WebDNA] DNA suffix


Well, for my 2 cents, I'm new to= WebDNA, but I have to agree with Christophe. I have programmed in asp, asp= x & 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 afte= r not working on it for a couple of years.

Additionally, I like know= ing 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, th= e 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 do= n't recognize, I often look it up to see what it is.

And finally, ab= out using .html. I would not recommend that. We all have control over our s= ervers it would appear. However, in a shared hosting environment you often = don't. If WebDNA ever gets widely adopted, the hosting companies are not go= ing to map .html to webDNA - just like they don't do it for asp or php. Als= o, 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 possibl= e) 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

-----Orig= inal Message-----
From: Christophe Billiottet
Date: Wednesday, Sep 17, 2008 10:50 am
Subject: Re: [WebDNA] = DNA suffix
To: Reply-To:

Well, t= his was just that WebDNA, as a web scripting language, is far
far behin= d the others in terms of number of active servers and sites.
If you che= ck a php site, there is nothing different between it and any
other html= site, except for the .php suffix that makes it immediately
identifiabl= e: "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 seem= s everybody is satisfied with it.
Same with .asp

The suffix iden= tifies a technology, and we, WebDNA users, decided to
hide our technolo= gy.

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 a= gree with Dan.

> I would certainly support setting .dna as the de= fault suffix - but I
like the fact that my sites are not clearly identi= fied with any
technology. I also hide the bit w= ith
WebDNA comments so there should be no easy way for a user to
de= termine the server side scripting language used.

> I would think = this would be considered good security practice.

> - Tom

&= gt;

---------------------------------------------------------
Thi= s message is sent to you because you are subscribed to
the mailing list = .
To unsubscribe, E-mail to:
a= rchives: http://mail.webdna.us/list/talk@webdna.us
old archives: http://= dev.webdna.us/TalkListArchive/



-----------------------------= ----------------------------
This message is sent to you because you are= subscribed to
the mailing list .
To unsubscribe, E-m= ail to:
archives: http://mail.webdna.us/list/talk= @webdna.us
old archives: http://dev.webdna.us/TalkListArchive/

------=_NextPart_000_0001_3711BCAF.2A9F77AE-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] DNA suffix ("Dan Strong" 2008)
  2. Re: [WebDNA] DNA suffix (Dylan Wood 2008)
  3. Re: [WebDNA] DNA suffix (Donovan Brooke 2008)
  4. Re: [WebDNA] DNA suffix (Paul Willis 2008)
  5. Re: [WebDNA] DNA suffix (Eddie Z 2008)
  6. Re: [WebDNA] DNA suffix (Bob Minor 2008)
  7. Re: [WebDNA] DNA suffix (Chris 2008)
  8. Re: [WebDNA] DNA suffix ("Robert Sweet" 2008)
  9. Re: [WebDNA] DNA suffix (Chris 2008)
  10. Re: [WebDNA] DNA suffix ("Psi Prime, Matthew A Perosi " 2008)
  11. Re: [WebDNA] DNA suffix (Chris 2008)
  12. Re: [WebDNA] DNA suffix ("PLANET DJ (Chris W.)" 2008)
  13. RE: [WebDNA] DNA suffix ("Will Starck" 2008)
  14. Re: [WebDNA] DNA suffix (Dylan Wood 2008)
  15. Re: [WebDNA] DNA suffix (Dylan Wood 2008)
  16. Re: [WebDNA] DNA suffix ("Robert Sweet" 2008)
  17. Re: [WebDNA] DNA suffix (Tim Benson 2008)
  18. RE: [WebDNA] DNA suffix ("Will Starck" 2008)
  19. Re: [WebDNA] DNA suffix ("JD Ready" 11:3)
  20. Re: [WebDNA] DNA suffix ("Dan Strong" 2008)
  21. Re: [WebDNA] DNA suffix (Terry Wilson 2008)
  22. Re: [WebDNA] DNA suffix (Chris 2008)
  23. Re: [WebDNA] DNA suffix (Terry Wilson 2008)
  24. Re: [WebDNA] DNA suffix (Donovan Brooke 2008)
  25. Re: [WebDNA] DNA suffix ("Tom Duke" 2008)
  26. Re: [WebDNA] DNA suffix ("William DeVaul" 2008)
  27. Re: [WebDNA] DNA suffix (Donovan Brooke 2008)
  28. Re: [WebDNA] DNA suffix ("Dan Strong" 2008)
  29. Re: [WebDNA] DNA suffix (Chris 2008)
  30. Re: [WebDNA] DNA suffix ("Psi Prime, Matthew A Perosi " 2008)
  31. Re: [WebDNA] DNA suffix (Chris 2008)
  32. Re: [WebDNA] DNA suffix (Paul Willis 2008)
  33. RE: [WebDNA] DNA suffix ("Michael A. DeLorenzo" 2008)
  34. [WebDNA] DNA suffix (Chris 2008)
This is a multipart message in MIME format. ------=_NextPart_000_0001_3711BCAF.2A9F77AE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I agree with all that was said, EXCEPT... I certainly don't want to lose my Google Page Rank and SEO just because the software platform wants to change extensions. I would gladly code new sites using .dna, but the existing ones need to stay as .tpl. Best Regards, Chris Whybrew Senior Account Manager PLANET DJ INC www.planetdj.com p: 775.323.1540 ext 3903 f: 775.323.8230 e: chrisw@planetdj.com ---------------------------------------- From: "JD Ready" Sent: Wednesday, September 17, 2008 10:32 AM To: talk@webdna.us Subject: Re: [WebDNA] DNA suffix 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/ --------------------------------------------------------- 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/ ------=_NextPart_000_0001_3711BCAF.2A9F77AE Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I agree with all that was said, EXCEPT... I certainly don't want t= o lose my Google Page Rank and SEO just because the software platform wants= to change extensions. I would gladly code new sites using .dna, but the ex= isting ones need to stay as .tpl.

Best Regards,

Chris= Whybrew
Senior Account Manager


PLANET= DJ INC
= www.planetdj.com

= p: 775.323.1540 ext 3903
f: 775.323= .8230
e:
<= FONT face=3DVerdana color=3D#497699>chrisw@planetdj.com




From: "JD Ready" <jdready@risedev.com>
Sent: Wednesd= ay, September 17, 2008 10:32 AM
To: talk@webdna.us
Subject<= /B>: Re: [WebDNA] DNA suffix


Well, for my 2 cents, I'm new to= WebDNA, but I have to agree with Christophe. I have programmed in asp, asp= x & 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 afte= r not working on it for a couple of years.

Additionally, I like know= ing 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, th= e 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 do= n't recognize, I often look it up to see what it is.

And finally, ab= out using .html. I would not recommend that. We all have control over our s= ervers it would appear. However, in a shared hosting environment you often = don't. If WebDNA ever gets widely adopted, the hosting companies are not go= ing to map .html to webDNA - just like they don't do it for asp or php. Als= o, 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 possibl= e) 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

-----Orig= inal Message-----
From: Christophe Billiottet
Date: Wednesday, Sep 17, 2008 10:50 am
Subject: Re: [WebDNA] = DNA suffix
To: Reply-To:

Well, t= his was just that WebDNA, as a web scripting language, is far
far behin= d the others in terms of number of active servers and sites.
If you che= ck a php site, there is nothing different between it and any
other html= site, except for the .php suffix that makes it immediately
identifiabl= e: "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 seem= s everybody is satisfied with it.
Same with .asp

The suffix iden= tifies a technology, and we, WebDNA users, decided to
hide our technolo= gy.

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 a= gree with Dan.

> I would certainly support setting .dna as the de= fault suffix - but I
like the fact that my sites are not clearly identi= fied with any
technology. I also hide the bit w= ith
WebDNA comments so there should be no easy way for a user to
de= termine the server side scripting language used.

> I would think = this would be considered good security practice.

> - Tom

&= gt;

---------------------------------------------------------
Thi= s message is sent to you because you are subscribed to
the mailing list = .
To unsubscribe, E-mail to:
a= rchives: http://mail.webdna.us/list/talk@webdna.us
old archives: http://= dev.webdna.us/TalkListArchive/



-----------------------------= ----------------------------
This message is sent to you because you are= subscribed to
the mailing list .
To unsubscribe, E-m= ail to:
archives: http://mail.webdna.us/list/talk= @webdna.us
old archives: http://dev.webdna.us/TalkListArchive/

------=_NextPart_000_0001_3711BCAF.2A9F77AE-- "PLANET DJ (Chris W.)"

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:

Document Contains no data, or showcart error. (1997) Storing calculated data (2002) test (2000) japanese characters (1997) Setting up the server (1997) WebCatb15 Mac CGI -- [purchase] (1997) combining strings (1997) Size limit for tmpl editor ? (1997) search zip codes ranges (2003) Why does WebCat do this? (2001) emailer (1997) Problems with 2.1b4 (1997) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997) Enhancement Request for WebCatalog-NT (1996) [WebDNA] Only one request at a time? (2011) Secure Server not remembering discounts (1998) A link and two command (1998) formatting dates from a field ... (1997) Auto entering Friday's date in a field (2002) UPS (2003)