Re: [WebDNA] Just drop the Server version

This WebDNA talk-list message is from

2015


It keeps the original formatting.
numero = 112125
interpreted = N
texte = --Apple-Mail=_9F05A4B7-B194-4C14-8A0F-67B87E8F7F22 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I, too, have developed a CMS that I use under all the sites I develop. = It is absolutely required that all these sites share the same code and = databases located in the globals directory. So while I understand the = arguments that code should be sandboxed for security and such, there are = a class of applications that absolutely need to operate outside of a = per-domain barrier. Server version is vital for anyone developing such = applications. Mike > On Feb 11, 2015, at 10:27 AM, Dan Strong wrote: >=20 > I don't think we need to worry about new users, Matt ;-p >=20 > -Dan Strong > http://danstrong.com > http://sw.amphou.se > On Wed, Feb 11, 2015 at 4:56 AM, Matthew A Perosi, Psi Prime = > wrote: > "It starts to fall off the rails a little as web projects get bigger" >=20 > I totally disagree with this statement. >=20 > In 1997 I started to engineer a CMS built on top of SiteBuilder. By = 2008 that CMS had grown unmanageable and slow. So it was rebuild line = by line using the experience gained from the first 11 years. >=20 > Even my first generation CMS did some pretty amazing things. When = I've pitched my CMS against others, the speed and functionality I have = wins. >=20 > I don't want to start an argument or a debate here, I just don't want = any new WebDNA users to get the wrong idea if they happen to read this = thread. >=20 >=20 > -Matt >=20 >=20 >=20 >=20 >=20 > On 2/10/2015 10:01 PM, Brian Burton wrote: > Getting rid of the server version makes WebDNA a less attractive = language. >=20 > Let me explain. WebDNA=E2=80=99s databases system is very easy to use = for web programmers of simple to moderate web sites. It starts to fall = off the rails a little as web projects get bigger, but for those of us = that love the simplicity of WebDNA, we find ways to make it work (using = the globals folder to have path agnostic databases, sharding databases = to make them small and speedy, etc) >=20 > My understanding of the FCGI is it starts a process and loads into = memory the databases it needs for 1 domain(website). Multiple instances = of the FCI to support multiple front ends for one set of databases (via = a shared universal globals folder (is that even possible with the FCGI?) = would cause all sorts of data inconsistency problems. >=20 > Brian B. Burton >=20 >=20 > On Feb 10, 2015, at 10:01 AM, Kenneth Grome > wrote: >=20 > Hi tom, >=20 > Fortunately you have a brand new Server version 8.0.2 that works > for you now, and I suspect that this version will hold you for > another 5-10 years, even if no new Server version were ever > developed or released, correct? >=20 > Another issue here is that if WSC would make "^" work in the > FastCGI version (the way it works in the Server version) you'd be > able to run the FastCGI version for your CMS, correct? >=20 > When I suggested no more development on the Server version I was > offering a supporting option for Chris' goal when he said: >=20 > "We want to keep things as simple as possible." >=20 > One way to dramatically simplify WSC's software development work > (and save a ton of money) is to stop developing all versions > except one. And since the FastCGI version runs on the most > popular servers on the web these days, it would seem to "make > sense" to continue to develop only the FastCGI version. >=20 > I think Chris has finally gotten WSC back on-track for success > again. We are certainly seeing more development now than during > the previous two or three years! I would hate to see all this new > development 'disappear' because the company tries to stretch their > resources too thin. >=20 > This is a hard decision, I know, but sometimes hard decisions must > be made in order for a company to survive. And I for one would > like to see the company not just survive but thrive! >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Management > --------------------------------------------------------- > 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 >=20 >=20 > --=20 > Matthew A Perosi > Corporate Consultant > Mobile Marketing Expert > Senior Web Developer > SEO Analyst & Educator > matt@psiprime.com >=20 > Psi Prime, Inc. > 323 Union Blvd. > Totowa, NJ 07512 >=20 > Direct: 888.872.0274 > Fax: 888.488.5924 >=20 > http://www.perosi.com > --------------------------------------------------------- > 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 --Apple-Mail=_9F05A4B7-B194-4C14-8A0F-67B87E8F7F22 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I, too, have developed a CMS that I use under all the sites I = develop.  It is absolutely required that all these sites share the = same code and databases located in the globals directory.  So while = I understand the arguments that code should be sandboxed for security = and such, there are a class of applications that absolutely need to = operate outside of a per-domain barrier.  Server version is vital = for anyone developing such applications.

Mike


On Feb 11, 2015, at 10:27 AM, = Dan Strong <dan@danstrong.com> wrote:

I don't think we need to worry about new users, Matt = ;-p


On Wed, Feb 11, 2015 at 4:56 = AM, Matthew A Perosi, Psi Prime <matt@psiprime.com> wrote:
"It = starts to fall off the rails a little as web projects get bigger"

I totally disagree with this statement.

In 1997 I started to engineer a CMS built on top of SiteBuilder.  = By 2008 that CMS had grown unmanageable and slow.  So it was = rebuild line by line using the experience gained from the first 11 = years.

Even my first generation CMS did some pretty amazing things.  When = I've pitched my CMS against others, the speed and functionality I have = wins.

I don't want to start an argument or a debate here, I just don't want = any new WebDNA users to get the wrong idea if they happen to read this = thread.


-Matt





On 2/10/2015 10:01 PM, Brian Burton wrote:
Getting rid of the server version makes WebDNA a less attractive = language.

Let me explain. WebDNA=E2=80=99s databases system is very easy to use = for web programmers of simple to moderate web sites. It starts to fall = off the rails a little as web projects get bigger, but for those of us = that love the simplicity of WebDNA, we find ways to make it work (using = the globals folder to have path agnostic databases, sharding databases = to make them small and speedy, etc)

My understanding of the FCGI is it starts a process and loads into = memory the databases it needs for 1 domain(website). Multiple instances = of the FCI to support multiple front ends for one set of databases (via = a shared universal globals folder (is that even possible with the FCGI?) = would cause all sorts of data inconsistency problems.

Brian B. Burton


On Feb 10, 2015, at 10:01 AM, Kenneth Grome <ken@webdnasolutions.com> wrote:

Hi tom,

Fortunately you have a brand new Server version 8.0.2 that works
for you now, and I suspect that this version will hold you for
another 5-10 years, even if no new Server version were ever
= developed or released, correct?

Another issue here is that if WSC would make "^" work in the
FastCGI version (the way it works in the Server version) you'd be
able to run the FastCGI version for your CMS, correct?

When I suggested no more development on the Server version I was
offering a supporting option for Chris' goal when he said:

"We want to keep things as simple as possible."

One way to dramatically simplify WSC's software development work
(and save a ton of money) is to stop developing all versions
except one.  And since the FastCGI version runs on the most
popular servers on the web these days, it would seem to "make
sense" to continue to develop only the FastCGI version.

I think Chris has finally gotten WSC back on-track for success
again.  We are certainly seeing more development now than during
the previous two or three years!  I would hate to see all this = new
development 'disappear' because the company tries to stretch their
resources too thin.

This is a hard decision, I know, but sometimes hard decisions must
be made in order for a company to survive.  And I for one would
like to see the company not just survive but thrive!

Regards,
Kenneth Grome
WebDNA Solutions
http://www.webdnasolutions.com
Web Database Systems and Linux Server Management
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us



--
Matthew A Perosi
Corporate Consultant
Mobile Marketing Expert
Senior Web Developer
SEO Analyst & Educator
matt@psiprime.com

Psi Prime, Inc.
323 Union Blvd.
Totowa, NJ 07512

Direct:  888.872.0274
Fax:     888.488.5924

http://www.perosi.com
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us

--------------------------------------------------------- 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

= --Apple-Mail=_9F05A4B7-B194-4C14-8A0F-67B87E8F7F22-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Just drop the Server version (Michael Davis 2015)
  2. Re: [WebDNA] Just drop the Server version (Dan Strong 2015)
  3. Re: [WebDNA] Just drop the Server version ("Matthew A Perosi, Psi Prime" 2015)
  4. Re: [WebDNA] Just drop the Server version (Palle 2015)
  5. Re: [WebDNA] Just drop the Server version (Kenneth Grome 2015)
  6. Re: [WebDNA] Just drop the Server version (christophe.billiottet@webdna.us 2015)
  7. Re: [WebDNA] Just drop the Server version (Brian Burton 2015)
  8. Re: [WebDNA] Just drop the Server version (Kenneth Grome 2015)
  9. Re: [WebDNA] Just drop the Server version (Tom Duke 2015)
  10. [WebDNA] Just drop the Server version (Kenneth Grome 2015)
--Apple-Mail=_9F05A4B7-B194-4C14-8A0F-67B87E8F7F22 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I, too, have developed a CMS that I use under all the sites I develop. = It is absolutely required that all these sites share the same code and = databases located in the globals directory. So while I understand the = arguments that code should be sandboxed for security and such, there are = a class of applications that absolutely need to operate outside of a = per-domain barrier. Server version is vital for anyone developing such = applications. Mike > On Feb 11, 2015, at 10:27 AM, Dan Strong wrote: >=20 > I don't think we need to worry about new users, Matt ;-p >=20 > -Dan Strong > http://danstrong.com > http://sw.amphou.se > On Wed, Feb 11, 2015 at 4:56 AM, Matthew A Perosi, Psi Prime = > wrote: > "It starts to fall off the rails a little as web projects get bigger" >=20 > I totally disagree with this statement. >=20 > In 1997 I started to engineer a CMS built on top of SiteBuilder. By = 2008 that CMS had grown unmanageable and slow. So it was rebuild line = by line using the experience gained from the first 11 years. >=20 > Even my first generation CMS did some pretty amazing things. When = I've pitched my CMS against others, the speed and functionality I have = wins. >=20 > I don't want to start an argument or a debate here, I just don't want = any new WebDNA users to get the wrong idea if they happen to read this = thread. >=20 >=20 > -Matt >=20 >=20 >=20 >=20 >=20 > On 2/10/2015 10:01 PM, Brian Burton wrote: > Getting rid of the server version makes WebDNA a less attractive = language. >=20 > Let me explain. WebDNA=E2=80=99s databases system is very easy to use = for web programmers of simple to moderate web sites. It starts to fall = off the rails a little as web projects get bigger, but for those of us = that love the simplicity of WebDNA, we find ways to make it work (using = the globals folder to have path agnostic databases, sharding databases = to make them small and speedy, etc) >=20 > My understanding of the FCGI is it starts a process and loads into = memory the databases it needs for 1 domain(website). Multiple instances = of the FCI to support multiple front ends for one set of databases (via = a shared universal globals folder (is that even possible with the FCGI?) = would cause all sorts of data inconsistency problems. >=20 > Brian B. Burton >=20 >=20 > On Feb 10, 2015, at 10:01 AM, Kenneth Grome > wrote: >=20 > Hi tom, >=20 > Fortunately you have a brand new Server version 8.0.2 that works > for you now, and I suspect that this version will hold you for > another 5-10 years, even if no new Server version were ever > developed or released, correct? >=20 > Another issue here is that if WSC would make "^" work in the > FastCGI version (the way it works in the Server version) you'd be > able to run the FastCGI version for your CMS, correct? >=20 > When I suggested no more development on the Server version I was > offering a supporting option for Chris' goal when he said: >=20 > "We want to keep things as simple as possible." >=20 > One way to dramatically simplify WSC's software development work > (and save a ton of money) is to stop developing all versions > except one. And since the FastCGI version runs on the most > popular servers on the web these days, it would seem to "make > sense" to continue to develop only the FastCGI version. >=20 > I think Chris has finally gotten WSC back on-track for success > again. We are certainly seeing more development now than during > the previous two or three years! I would hate to see all this new > development 'disappear' because the company tries to stretch their > resources too thin. >=20 > This is a hard decision, I know, but sometimes hard decisions must > be made in order for a company to survive. And I for one would > like to see the company not just survive but thrive! >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Management > --------------------------------------------------------- > 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 >=20 >=20 > --=20 > Matthew A Perosi > Corporate Consultant > Mobile Marketing Expert > Senior Web Developer > SEO Analyst & Educator > matt@psiprime.com >=20 > Psi Prime, Inc. > 323 Union Blvd. > Totowa, NJ 07512 >=20 > Direct: 888.872.0274 > Fax: 888.488.5924 >=20 > http://www.perosi.com > --------------------------------------------------------- > 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 --Apple-Mail=_9F05A4B7-B194-4C14-8A0F-67B87E8F7F22 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I, too, have developed a CMS that I use under all the sites I = develop.  It is absolutely required that all these sites share the = same code and databases located in the globals directory.  So while = I understand the arguments that code should be sandboxed for security = and such, there are a class of applications that absolutely need to = operate outside of a per-domain barrier.  Server version is vital = for anyone developing such applications.

Mike


On Feb 11, 2015, at 10:27 AM, = Dan Strong <dan@danstrong.com> wrote:

I don't think we need to worry about new users, Matt = ;-p


On Wed, Feb 11, 2015 at 4:56 = AM, Matthew A Perosi, Psi Prime <matt@psiprime.com> wrote:
"It = starts to fall off the rails a little as web projects get bigger"

I totally disagree with this statement.

In 1997 I started to engineer a CMS built on top of SiteBuilder.  = By 2008 that CMS had grown unmanageable and slow.  So it was = rebuild line by line using the experience gained from the first 11 = years.

Even my first generation CMS did some pretty amazing things.  When = I've pitched my CMS against others, the speed and functionality I have = wins.

I don't want to start an argument or a debate here, I just don't want = any new WebDNA users to get the wrong idea if they happen to read this = thread.


-Matt





On 2/10/2015 10:01 PM, Brian Burton wrote:
Getting rid of the server version makes WebDNA a less attractive = language.

Let me explain. WebDNA=E2=80=99s databases system is very easy to use = for web programmers of simple to moderate web sites. It starts to fall = off the rails a little as web projects get bigger, but for those of us = that love the simplicity of WebDNA, we find ways to make it work (using = the globals folder to have path agnostic databases, sharding databases = to make them small and speedy, etc)

My understanding of the FCGI is it starts a process and loads into = memory the databases it needs for 1 domain(website). Multiple instances = of the FCI to support multiple front ends for one set of databases (via = a shared universal globals folder (is that even possible with the FCGI?) = would cause all sorts of data inconsistency problems.

Brian B. Burton


On Feb 10, 2015, at 10:01 AM, Kenneth Grome <ken@webdnasolutions.com> wrote:

Hi tom,

Fortunately you have a brand new Server version 8.0.2 that works
for you now, and I suspect that this version will hold you for
another 5-10 years, even if no new Server version were ever
= developed or released, correct?

Another issue here is that if WSC would make "^" work in the
FastCGI version (the way it works in the Server version) you'd be
able to run the FastCGI version for your CMS, correct?

When I suggested no more development on the Server version I was
offering a supporting option for Chris' goal when he said:

"We want to keep things as simple as possible."

One way to dramatically simplify WSC's software development work
(and save a ton of money) is to stop developing all versions
except one.  And since the FastCGI version runs on the most
popular servers on the web these days, it would seem to "make
sense" to continue to develop only the FastCGI version.

I think Chris has finally gotten WSC back on-track for success
again.  We are certainly seeing more development now than during
the previous two or three years!  I would hate to see all this = new
development 'disappear' because the company tries to stretch their
resources too thin.

This is a hard decision, I know, but sometimes hard decisions must
be made in order for a company to survive.  And I for one would
like to see the company not just survive but thrive!

Regards,
Kenneth Grome
WebDNA Solutions
http://www.webdnasolutions.com
Web Database Systems and Linux Server Management
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us



--
Matthew A Perosi
Corporate Consultant
Mobile Marketing Expert
Senior Web Developer
SEO Analyst & Educator
matt@psiprime.com

Psi Prime, Inc.
323 Union Blvd.
Totowa, NJ 07512

Direct:  888.872.0274
Fax:     888.488.5924

http://www.perosi.com
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us

--------------------------------------------------------- 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

= --Apple-Mail=_9F05A4B7-B194-4C14-8A0F-67B87E8F7F22-- Michael Davis

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:

using showpage and showcart commands (1996) Help! WebCat2 bug (1997) [WebDNA] sudo WebCatalogCtl stop won't work (2016) RAM variables (1997) catagories (1997) Just a thought (1998) WebDNA 4.5.1 Now Available (2003) emailer on Windows Beta 18 (1997) For those of you not on the WebCatalog Beta... (1997) download a file (2001) [WebDNA] Problem with [ListDatabases] - WebDNA CE 6.0a - Windows (2010) Why do extra quotation marks sometimes appear in my databases? (1998) (OT) SERVER FREEZES ALL AT SAME TIME (2004) Re(4): grep matching (2003) Search Engine questions ... (2002) emailer (1997) Dup cart id on multi browsers running on the same machine-win2k (2001) 3RD POST Character limit in [Search]? (1998) webcat2b12 CGI -- Date comparisons (1997) Accented chars and emailer (1998)