Re: [WebDNA] WebDNA 7
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107548
interpreted = N
texte = Hi Stuart! these are two different designs; the way you built your = application, with some shared files in /global is convenient for the = designer/developer hosting all his customers on his own servers. Exactly = as WebDNA 6.x is centralized (one copy shared among the server's sites) = with one main admin and sandboxes subadmin: it is a complicated dedign = that fits a specific and very restrictive case. I blame this design to partly explain the lack of WebDNA spreading: it = needs a dedicated server, the customer is highly dependant, very few = hosting providers are providing WebDNA service. Other consequences are = the difficulty to locate code that bugs an entire server down (because = the module brings apache down with it) At the cost of having some duplicates (that could be easily located in a = local /global directory that could be replicated as you wish in any = number of websites), these problems should be over: customers can now = have their own WebDNA copy, they can use almost whatever webserver they = want, WebDNA should now be welcome by most hosting providers, a local = WebDNA code problem will not affect an entire server anymore, customers = have full control over their administration and are free to move their = WebDNA code wherever they want. Now, imagine php users were tied to their developer if this one would = keep their application code in two different directories: their website = and an invisible directory where the programer would keep strategic = files. It might be convenient, but the customer would probably feel = "trapped" and php would not have the success it has. In my opinion, if you need to keep some strategic files away from the = customer's eyes, the [encrypt] tag is there to protect your templates, = and the customer will be free to move as long as he moves the encrypted = templates with him. In conclusion, i do not think the 6.x /global directory can save = programming time (by building a standard and local /global), is not = really saving space neither (few hundred kB?), implies major complexity = for WebDNA and restrict customer's freedom. Since it is very easy to = move locally the /global directory and fix the references to it with a = single "search and replace" in few minutes only, i really do not = understand the fellows here who feel that the world would stop without = /global. - chris On Oct 26, 2011, at 0:18, Stuart Tremain wrote: > Or I could just edit 1 file in one place and know that every site will = then be updated without having to "publish" updates to other sites = ....... >=20 >=20 > On 26/10/2011, at 1:07 PM, Kenneth Grome wrote: >=20 >>> I built that system as an "Enterprise" system so that >>> anyone that had a forum would be using the same include >>> files and some data from shared dbs all served from the >>> globals directory. >>=20 >> You could always create a set of starter files for v7 forums,=20 >> then duplicate those files every time someone gets his/her=20 >> own new forum. =20 >>=20 >> This would make it easier to improve the system as you go=20 >> along too, because existing forums would use different files=20 >> than the newer ones. >>=20 >> Sincerely, >> Kenneth Grome >> --------------------------------------------------------- >> 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 >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > 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 > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
Hi Stuart! these are two different designs; the way you built your = application, with some shared files in /global is convenient for the = designer/developer hosting all his customers on his own servers. Exactly = as WebDNA 6.x is centralized (one copy shared among the server's sites) = with one main admin and sandboxes subadmin: it is a complicated dedign = that fits a specific and very restrictive case. I blame this design to partly explain the lack of WebDNA spreading: it = needs a dedicated server, the customer is highly dependant, very few = hosting providers are providing WebDNA service. Other consequences are = the difficulty to locate code that bugs an entire server down (because = the module brings apache down with it) At the cost of having some duplicates (that could be easily located in a = local /global directory that could be replicated as you wish in any = number of websites), these problems should be over: customers can now = have their own WebDNA copy, they can use almost whatever webserver they = want, WebDNA should now be welcome by most hosting providers, a local = WebDNA code problem will not affect an entire server anymore, customers = have full control over their administration and are free to move their = WebDNA code wherever they want. Now, imagine php users were tied to their developer if this one would = keep their application code in two different directories: their website = and an invisible directory where the programer would keep strategic = files. It might be convenient, but the customer would probably feel = "trapped" and php would not have the success it has. In my opinion, if you need to keep some strategic files away from the = customer's eyes, the [encrypt] tag is there to protect your templates, = and the customer will be free to move as long as he moves the encrypted = templates with him. In conclusion, i do not think the 6.x /global directory can save = programming time (by building a standard and local /global), is not = really saving space neither (few hundred kB?), implies major complexity = for WebDNA and restrict customer's freedom. Since it is very easy to = move locally the /global directory and fix the references to it with a = single "search and replace" in few minutes only, i really do not = understand the fellows here who feel that the world would stop without = /global. - chris On Oct 26, 2011, at 0:18, Stuart Tremain wrote: > Or I could just edit 1 file in one place and know that every site will = then be updated without having to "publish" updates to other sites = ....... >=20 >=20 > On 26/10/2011, at 1:07 PM, Kenneth Grome wrote: >=20 >>> I built that system as an "Enterprise" system so that >>> anyone that had a forum would be using the same include >>> files and some data from shared dbs all served from the >>> globals directory. >>=20 >> You could always create a set of starter files for v7 forums,=20 >> then duplicate those files every time someone gets his/her=20 >> own new forum. =20 >>=20 >> This would make it easier to improve the system as you go=20 >> along too, because existing forums would use different files=20 >> than the newer ones. >>=20 >> Sincerely, >> Kenneth Grome >> --------------------------------------------------------- >> 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 >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > 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 > Bug Reporting: support@webdna.us
christophe.billiottet@webdna.us
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:
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
problems with 2 tags (1997)
WebCat b13 CGI -shownext- (1997)
Not accepting Zero (2000)
WebCatalog/Mac 2.1b2 New Features (1997)
Supressing Error Messages (1998)
RE: [isfolder] and [filename] (1997)
show all problem (1997)
Follow-up to listfiles bug report ... (2003)
Setting vars in a text file..... (2004)
where to put code (1998)
WCS Newbie question (1997)
Cart date/time (2006)
Some Questions (1997)
Secure Sever and showcart errors (1997)
[REPLACE] inside [FOUNDITEMS] (1998)
this works sometimes and sometimes not (1997)
[WebDNA] unsubscribe (2008)
Re:Emailer and encryption (1997)
any idea (2004)