D
dbeavon
Guest
True, if you've never experienced remote client/server database connectivity (-H -S) then that will be a very long learning process. It takes quite a bit of time to configure the database startup parameters ("SERV"ers) to support remote clients properly. And, on the development side of things, all your ABL runs quite a lot slower than it does with "shared memory". There are also a number of management-related issues that you may be confronted with. For example, "shared memory" clients are auto-trimmed whenever the database is restarted, but your remote client/server processes may need to be restarted manually because they don't recover very well on their own. If this is a new application, and you can afford the licenses, then you may want to look at investing in PASOE rather than "classic" appserver. PASOE has a lot of features that you might benefit from. The features may even allow you to bypass WCF in the scenarios where WCF is doing nothing more than working as a middle man. Personally I love WCF and would probably use it either way, unless it caused additional problems.
Continue reading...
Continue reading...