×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: James Perkins
I guess I need to understand what you mean by "native".
I know your question was to Mark Lazarus, but "native" means jobs & threads that run under the native virtual machine as opposed to the Java virtual machine, or the Unix virtual machine (PASE). And as opposed to deploying applications that run in a separate interpreted environment - like PHP.
Native has traditionally meant a transparent interface between workstations and database tables - where workstation I/O and database I/O share the same I/O buffers - or at least appear that way.
Most folks these days divide applications into separate components, running in separate virtual machines (perhaps even on separate physical platforms), using separate address spaces, communicating over sockets, and saving/restoring session data across client requests. But that kind of development is the antithesis of what a "native" developer would do.
Running entire applications in the same address space offers performance, reliability, deployment, and workload management advantages over distributed architectures. Not that people give a hoot for those things. They'd rather go merrily along, doing what most other people do.
Nathan.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
