I think you should use the correct tool for the correct job. If you are creating an application that will ship as a single .EXE and run as traditional file/server or client/server (two tier) then use CB6.1, there would be to much overhead in COMCodebook.
But, if you are planning to take the app multi-tier or run it with a web or other front end, then you should start the ap with COMCodebook which is designed to run this way. Could you use CB6.1 for n-Tier, well yes, but it wouldn't scale very well due to the statefull nature of the business objects. Also, there is no support in the bizobj's for MTS.. (That I know of.)
<i><font color="#663300">Really I started using CB 6.1 instead of COMCodebook because I thought that will be easier to start an app. I thought that COMCodebook will deal with more complex concepts of data technologies that the one I need by the moment (just DBF). Really I'm thinking to use COMCodebook in a second step.
Perhaps do you think this is a wrong way? Is it preferable to start with COMCodebook?
<i><font color="#663300">
The problem with the security in CB 6.1 is that it is implmented in the UI and not the business layer, which is where it belongs. Also, binding the controls to the view/table fields breaks n-tier.
I think the security should be implemented with some type of hook pattern, this way it could be hooked into a control of hooked into the business layer.
So, if n-Tier is your goal, I guess I would say, don't use CB 6.1, move to COM Codebook. CB 6.1 still needs a bit of work to support physical nTier aps.
So, what am I saying, I guess I am saying, use what works for you.
BOb
</font></i>
</font></i>
©2001 Bob Archer |
