Smithware's I*net Data Server is the fast and easy way to build database applications for the I*net (Internet-intranet). IDS provides true client/server database interaction over the I*net or any TCP/IP connection. It keeps you directly connected to your data without cumbersome scripting languages or multi-layered data access methods. If you want to build Internet connectivity into your Btrieve-based applications, or if you want to access Btrieve data over the Internet, then Smithware I*net Data Server is for you!
Client/Server Architecture Makes Smithware's I*net Data Server Simple.
The IDS Server component is a robust, multi-threaded, secure database server which runs as a Windows NT service. The IDS acts as a proxy between a Btrieve server and IDS clients and eliminates the need for Btrieve client configurations.
Look at Figure 1 and you'll notice the familiar architecture of IDS. The server component simply handles requests from clients (workstations), which are connected by a TCP/IP connection over the I*net to data stored in Btrieve files. It's that simple!
Because IDS client components are available
in three flavors: an ActiveX Client, a Java Client and a DLL Client, IDS developers get unparalleled flexibility in building powerful Btrieve database solutions for the I*net.
The ActiveX Client is a great choice for browserless database applications that use the I*net for the communications pathway between the application and data. The Java Client is the best choice for web/browser-based database applets, and the DLL Client allows you to I*net-enable legacy Btrieve applications. You have the flexibility to choose one or any combination of client components.
With this kind of flexibility, you can choose the best approach to fulfill your application requirements. Only IDS provides a unified solution for web (browser-based) and non-web (browserless) I*net database application development.
No Other Internet Database Solution Delivers True Client/Server Database Access Over The I*net Like IDS.
As you know, other approaches to building database applications for the I*net are often complicated and largely inefficient. (See Figure 2.) The use of scripting languages forces you to adopt an inefficient, indirect, multi-layered data access approach for what are normally simple database development tasks.
Programming difficulty is escalated by employing cumbersome, unfamiliar languages and programming environments. Plus, the inherent limitations in an HTML-based approach present you with little chance of real success, since HTML was never intended to accommodate database development.
IDS stands in contrast to other approaches, because it provides direct access to data over the I*net, just as you have over any other network. When designing IDS technology, we wondered, "Why should building a database application that runs over the Internet be any more difficult than one that runs over any other network?" When we looked at other approaches to I*net database development, we knew there had to be a better way. That's how IDS was born.
Look at Figure 3 and you can clearly see the direct approach IDS provides.
Notice that IDS gives you the same direct connection to your data that you have with your LAN based applications. This is IDS practicality at its best. With IDS, you simply build applications the way you always have.
IDS Puts You In Control Of Your Development Environment.
Using IDS gives you the power to choose your favorite development environment for your project. You can build I*net-enabled applications in virtually any Win32 and Java development environment including Visual Basic, Delphi, VC++, Borland C++ Builder, Visual Café, etc.
Build full-featured client/server database applications that are fully Internet-enabled using the development environment of your choice, eliminating the need to learn unfamiliar, web-specific programming languages. With IDS, you simply build I*net database applications the same way you're building your applications right now.