Common Platform Basis: Difference between revisions
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
<li> .Net/Visual Studio 8 (ASP, ASPX) | <li> .Net/Visual Studio 8 (ASP, ASPX) | ||
</ul> | </ul> | ||
<br> | |||
Our core platform services are made available in bindings for any of the above and our initial buildout will create a generic vertical for each distinct 'platform' choice above. | |||
<br><br> | <br><br> | ||
Note that only there are only 4 actual development packages above, and only 2 really full featured ones at that, but this is the way people currently shop for the basis for thier development needs, so we have to accomodate it. This focus is not without consequences but it cannot be helped because shopping for what you think you need instead of what you actually need is a buyer's prerogative. | Note that only there are only 4 actual development packages above, and only 2 really full featured ones at that, but this is the way people currently shop for the basis for thier development needs, so we have to accomodate it. This focus is not without consequences but it cannot be helped because shopping for what you think you need instead of what you actually need is a buyer's prerogative. | ||
<br><br> | <br><br> | ||
What you actually want, and may not know it, is a system that achieves your functional goals (assuming these are reasonable and feasible) and has the properties highlighted in the Value Prop(osition). In general what you may have think is the 'platform' choice or package du Jour generally has little to do with the attainment (except possibly to hinder it) of there properties. Nonetheless, unless such a choice presents a full blown conflict with the attainment of our | What you actually want, and may not know it, is a system that achieves your functional goals (assuming these are reasonable and feasible) and has the properties highlighted in the Value Prop(osition). In general what you may have think is the 'platform' choice or package du Jour generally has little to do with the attainment (except possibly to hinder it) of there properties. Nonetheless, unless such a choice presents a full blown conflict with the attainment of our | ||
<html><a href=/everything/index.pl?node=total+quality+management>Total Quality Management</a></html> goals, we can accomodate it. | <html><a href=/everything/index.pl?node=total+quality+management>Total Quality Management</a></html> goals, we can accomodate it. | ||
Revision as of 22:25, 17 April 2007
In addition to the Domain Content Mgt. System (DCMS) variants, the following application development packages are 'standard' with us and can be used to initialize your Enterprise domain:
- Director MX (Flash Dev)
- JBoss (J2EE, Java, JSP, Tomcat, etc.)
- Joomla, Drupal
- LAMP, RoR, or mod_perl
- .Net/Visual Studio 8 (ASP, ASPX)
Our core platform services are made available in bindings for any of the above and our initial buildout will create a generic vertical for each distinct 'platform' choice above.
Note that only there are only 4 actual development packages above, and only 2 really full featured ones at that, but this is the way people currently shop for the basis for thier development needs, so we have to accomodate it. This focus is not without consequences but it cannot be helped because shopping for what you think you need instead of what you actually need is a buyer's prerogative.
What you actually want, and may not know it, is a system that achieves your functional goals (assuming these are reasonable and feasible) and has the properties highlighted in the Value Prop(osition). In general what you may have think is the 'platform' choice or package du Jour generally has little to do with the attainment (except possibly to hinder it) of there properties. Nonetheless, unless such a choice presents a full blown conflict with the attainment of our
Total Quality Management goals, we can accomodate it.
