Peter Welcome aboard !!
Cache good points...... you must understand that CSP is a fully paid up (well people will argue that) oo database *AND* programming environment this is profound... real world data is represented in oo which much better models the real world than relational tables also.... programming a web interface has the same richness of polymorphism, encapsulation and inheritance separate from the data is verrrrrry powerful AND it's all in the same development environment AND (II) it quick, robust, scaleable ======= Bad points difficult learning curve - NOT Cache itself but oo design paradigm - to get the best out of both the data oo and programming oo needs lots of learning curve - but then again so does moving from ASP to ASP.NET Smaller mkarket - lots of widgets availiable for "mainstream products" Cache is a bit of "roll you own" Licensing model difficult (impossible) to compete with MySQL (free) - also see recent posts on licensing ====== Depends on what you are looking to develop What apps do you have in mind - small scale, simple ones - go for MySQL - industrial strength - go for Cache HTH and I am sure that there will be lots more posts !!! Peter On Mon, 16 Aug 2004 22:29:38 +0200, "Peter Haider" <[EMAIL PROTECTED]> wrote: >Hello Newsgroup, >currently now i am working with Classic ASP. >In most cases i use Mysql or MS SQL 2k. So far so good. >What i want to know, is it worth to evaluate Cache against .Net? >I think to migrate my application to DotNet, Cache could be also an option. >Do i stay with Dotnet on the right side or is this only a markting >statement? >And what is your experiance to position a product with Cache against DotNet >in the market, could i stand? >Hope to hear (read) a lot of your experiance. >Best regards >Peter Haider >
