D
dbeavon
Guest
I have often wondered about self-service vs remote connections with PASOE. Do you have any references which may say which is "better"? In the past a consultant had told us something different. He said that remote client/server connections are "better" for reasons related to database scalability and overall stability (no risks related to using kill -9 on client applications that may have "shared memory" with the RDBMS itself). I assume that this applies the same to PASOE applications as it does to any other type of client application that is connected to an OE database. Perhaps by "better" you simply mean "faster". I would agree that this is certainly true, since client/server connectivity to an OpenEdge database is pretty slow... it is extremely "chatty" relative to other client/server technologies that I've ever worked with ... and it seems to be *extremely* sensitive to network latency. Unlike with "self-service" connections, the remote ABL application is not allowed to communicate directly via shared memory, and the result is that ABL client/server connections don't perform very well over the network. (Even OE's "DataServer for SQL" seems faster over the network, but that is a different discussion.) I know that there are a variety of optimizations for OE client/server connections (parameters like Mm and prefetch) but it is still a challenge to make client/server apps behave responsively (this effort often involves a lot of code refactoring so that data is gathered proactively via FOREACH NOLOCK - which seems to be the "go-to" optimization technique). If you have any references that say which is better for PASOE (self-service or client/server) then I would love to read more on that topic.
Continue reading...
Continue reading...