Index: openacs-4/packages/ecommerce/www/doc/ecommerce-for-mbas.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/ecommerce/www/doc/ecommerce-for-mbas.adp,v diff -u -N -r1.4.4.1 -r1.4.4.2 --- openacs-4/packages/ecommerce/www/doc/ecommerce-for-mbas.adp 6 Mar 2005 21:39:38 -0000 1.4.4.1 +++ openacs-4/packages/ecommerce/www/doc/ecommerce-for-mbas.adp 6 Mar 2005 22:32:22 -0000 1.4.4.2 @@ -84,7 +84,7 @@ See http://www.arsdigita.com/doc/email-handler (via archive.org) an ACS 3.4.8 email handling perl script. Note that incoming emails may be better - handled by a method used in the OpenACS forums package that imports to email. No + handled by a method used in the OpenACS forums package that imports email. No support is available for incoming email to this package. @@ -159,17 +159,16 @@

Bottom line

-

If a closed-source ecommerce package doesn't do exactly what you - want, you're out of business. If the company behind a closed-source +

If a closed-source ecommerce package does not do exactly what you + want, you are out of business. If the company behind a closed-source ecommerce package goes out of business, so will you. If the company behind a closed-source ecommerce adopts a different "business - model", you're screwed.

+ model", you are screwed.

-

If you're even tempted to adopt a commercial ecommerce system +

If you are ever tempted to adopt a commercial ecommerce system from a company other than IBM, Oracle or SAP (three enterprise software vendors that seem likely to be around for awhile), read the - iCat story towards the end of Using the - ArsDigita Community System + iCat story; See http://www.arsdigita.com/asj/using-the-acs (via archive.org) toward the end, a section entitled "ACS versus Commercial Packaged Closed-Source Systems." +

-