Design help

From: Neil Talsania <neil.talsania_at_kodak.com>
Date: Tue, 30 Apr 2002 10:10:23 -0400
Message-ID: <aam8rh$dk4$1_at_news.kodak.com>

Hi,
[Quoted]   I am new to database work, and am looking for help in figuring out possible design options, or really what the best tool for the job might be.

[Quoted] The task is to fit into an existing client server application an oracle database on the server side. Basically the client picks a file on the server, a TCP/IP socket is opened and then the data is transmitted from the server to the client for display. What we want to do now, is have the user [Quoted] instead of sending a file name to the server, really send search criteria to the server. Eventually the client needs to get the data from the server in [Quoted] the same way it currently does. So, one thing might be for the server to [Quoted] return to the client the filename to open.

Now, my initial thoughts were to modify the client to get the attribute [Quoted] values to query on, transmit those to the client over the socket connection, modify the server to use embedded SQL to query the oracle database, and then [Quoted] [Quoted] return the results of the query again through the socket.

I am wondering if XML would make this any easier? If the client server interaction were web based, then I could see how it would be a huge benefit, [Quoted] but since it is not, I am not so sure. IF the client builds the xml file with the SQL embedded in the <query> tag, how does the server actually get [Quoted] the results of the query? How should it connect to the database server? Should it still use embedded SQL and parse the XML file, extract out the query, and then make the SQL call? Or can some of this happen automatically?

[Quoted] [Quoted] Any help or suggestions would be greatly appreciated.

Thanks
Neil Received on Tue Apr 30 2002 - 16:10:23 CEST