However. what if a developer has a preference for a certain other component-e.g MySnL (or PostgresSnL) for the RORMS. or some other app server instead of Tomcat? How do you plan to address this need?
However. what if a developer has a preference for a certain other component-e.g MySnL (or PostgresSnL) for the RORMS. or some other app server instead of Tomcat? How do you plan to address this need?
However. what if a developer has a preference for a certain other component-e.g MySnL (or PostgresSQL) for the RORMS. or some other app server instead of Tomcat? How do you plan to address this need?
Great question! The interesting thing about CAFE is that we did not take steps to prevent power users from adding, removing or swapping components. That capability is still there. In our humble opinion, in some cases, offering infinite choice and flexibility is where open source can sometimes suffer when compared to closed source competition. Please do not misunderstand us -- we feel choice is very important. We also feel that most people want an option that just works out of the box.
Our thinking is that the typical user we were trying to help would be well served by our choices. Those that want the software to just work should be pleased. Those that want to tinker could still do so. We recognise that some will be offended by the notion that we chose for them and conversely, many will be appreciative when the software just works. In the end, we never lost focus that it is the latter we were trying to help. We are counting on the community demand to pull us in the direction they want to go in this regard.
Bookmarks