Re: [PATCH] --with-ODBCRouter (database networking)

On Mon, 10 Jan 2005, Andi Gutmans wrote: Hi, > ...you should probably also provide PHP 5 diffs. Ok, we will queue this up. > Just out of curiosity, how does ODBC Router > differ from the other ODBC bridge solutions out > there? This could be off-topic, so we can only respond in summary and ask for any follow-ups to be directed only to info@augsoft.com + Early support of Macintosh meant that we had to be multi-network (TCP/IP, Appletalk, etc..), easy to use and, most importantly, able to support hundreds of high-end Motorola or IBM chips demanding data through a single Wintel box. We accomplish this with technology that keeps all of the inter-architecture data conversions (endian flipping, floating-point conversions, etc.) on the client-side, as opposed to allowing per-client conversions on the shared Wintel box. Our server architecture also makes use of system-level technologies like async I/O, multi-buffering, memory-mapped sections, multi-processing and multi-threading. To the Macs, PCs and Linux boxes it "just works" --to the database servers, the world continues to look Wintel. This enables Macs, PCs and Linux to always have access to the latest and greatest database drivers and support for the thousands of versions of hundreds of database systems on the market. + As far as the "other ODBC bridge solutions out there" go, one must realize that many of them have typically gone with all-ASCII/XML database sessions. This means they built their shared server components in a way that requires them to perform one-half of all of the data transformations for every client in the customer's network. ASCII/XML is perhaps the most expensive data transformation possible --and they have 1/2 of that occuring in shared server space. Because they have no optimizations for any specific architecture, it was also easy for their server components to run on a whole host of non-Windows platforms. This buys them a lot of political clout with customers who choose not to run Wintel boxes (even $299 DELLs bolted into a telco rack), nevermind the fact that database vendors do not consistently support non-Windows platforms (hence the very need for these kinds of solutions).