Board index Unix Web Servers

===HELP: How to port UNIX + Motif client/server app to a WWW app ?? ===

===HELP: How to port UNIX + Motif client/server app to a WWW app ?? ===

Post by C » Sat, 17 Jul 1999 04:00:00



Hello,

I'm interested to find out what might be the best
approach to convert a large Sun UNIX client-server TCP/IP
base C/C++/Motif/Sybase application over to a Web-based
application.

In particular, the client-server app consists of a client-
based X/Motif UNIX app which connects to a database
server application.  The client displays tabular and
graphical data as retrieved from the server application.
The client app makes TCP/IP and SQL calls to the server
which is running C/C++ and a Sybase RDMS.  The server
processes the client requests and then sends raw data
via TCP/IP for the client UNIX workstation to graphically
display with Motif v1.2 calls.

I'm interested in porting the client-server apps to a
PC/Apache + Linux + PHP3 + mySql + HTML environment in
which a Web browser can make requests to the Web server.
The Linux/Apache web server would create and send .gif
images of the data to the browser "on-the-fly". Tabular
data from the server would be sent to the browser via DHTML/
HTML/Java/PHP3, etc.

My hope is that:

1. the Sybase code could be ported to mySQL

2. the client and server C/C++ code could run almnost
as-is under Linux on the server

3. the Motif code could be ported to a freeware/Linux
version of Motif adn run almost as-is

4. the client UI code could be ported to HTML + a server
handlee

5. the Motif graphical output on the server could be
converted to .gifs on the server using some Motif -> .gif
converter code.  The .gif is then sent to the browser
per each browser request.

6. ...or some variation of the above or ??

Thanks in advance for any help/ideas/pointers on how
this porting process could be done most easily/quickly
given the different options I might have.


 
 
 
Top

===HELP: How to port UNIX + Motif client/server app to a WWW app ?? ===

Post by Jason Froeb » Sun, 18 Jul 1999 04:00:00



> Hello,

> I'm interested to find out what might be the best
> approach to convert a large Sun UNIX client-server TCP/IP
> base C/C++/Motif/Sybase application over to a Web-based
> application.

> In particular, the client-server app consists of a client-
> based X/Motif UNIX app which connects to a database
> server application.  The client displays tabular and
> graphical data as retrieved from the server application.
> The client app makes TCP/IP and SQL calls to the server
> which is running C/C++ and a Sybase RDMS.  The server
> processes the client requests and then sends raw data
> via TCP/IP for the client UNIX workstation to graphically
> display with Motif v1.2 calls.

> I'm interested in porting the client-server apps to a
> PC/Apache + Linux + PHP3 + mySql + HTML environment in
> which a Web browser can make requests to the Web server.
> The Linux/Apache web server would create and send .gif
> images of the data to the browser "on-the-fly". Tabular
> data from the server would be sent to the browser via DHTML/
> HTML/Java/PHP3, etc.

> My hope is that:

> 1. the Sybase code could be ported to mySQL

> 2. the client and server C/C++ code could run almnost
> as-is under Linux on the server

> 3. the Motif code could be ported to a freeware/Linux
> version of Motif adn run almost as-is

> 4. the client UI code could be ported to HTML + a server
> handlee

> 5. the Motif graphical output on the server could be
> converted to .gifs on the server using some Motif -> .gif
> converter code.  The .gif is then sent to the browser
> per each browser request.

> 6. ...or some variation of the above or ??

> Thanks in advance for any help/ideas/pointers on how
> this porting process could be done most easily/quickly
> given the different options I might have.



Hi,

Why not just use PHP to connect to the Sybase server?  You can keep the
Sybase SQL Server on the Sun box or move it over to Linux (ASE version
11.0.3.3).  D/L it from http://linux.sybase.com or http://www.suse.com

Jason

  jfroebe.vcf
< 1K Download

 
 
 
Top

1. VMS-to-Unix port of client/server-type app

     I'm in the process of porting a client/server-type app from
VMS to Unix, and want to make sure the new design is sensible
before committing a lot of code to it.
     The essential functionality is as follows: each client can
scroll through a table of database records -- one row on the screen
representing one record in the database.  Every time a record is
changed, that change is sent to the server, which then retransmits
it to everyone else, and their screens are updated accordingly.
     Each client waits for one of three events: either for a
datagram, or for a keystroke, or for a timer (required for some
ancillary functionality).
     Under VMS, a single process can handle all three.  That's
because VMS lets you associate an interrupt handler with each
event.  When one occurs, normal progarm flow is interrupted and the
handler is executed.  In my case, each of the three handlers gets
any data associated with the event, queues it up, and signals the
main program.  Main has been pausing, and wakes up when any handler
signals it.  Then it just loops, dequeuing and proccessing events
until the queue is empty.  Then it pauses again.  All this runs as
a single process.
     Under Unix, I believe I should fork a child for each type of
event, let the child block and wait for it, and then send the event
to the pausing parent, either on a message queue (neater) or using
shared memory (quicker).  Main _could_ handle the timer itself, but
a separate child for it would probably be neater.
     Is this the right idea for Unix?  I've got a lot of code to
port, and don't want to blunder into a cumbersome design, only to
be embarrassed by my ignorance after it's too late.  Any insight or
recommendations would be gratefully appreciated.
Thanks in advance,

2. Using a 3gb SCSI Hard Drive...

3. HOWTO restore /dev/hdb??

4. porting a unix client-server app.

5. Installing RH5.2 via ftp and TIS

6. unix apps, mac apps?

7. staroffice3.1

8. Motif app ported to Solaris 2.4 runs too slow

9. how to port owl to motif x-window app

10. How to port owl to motif x-window app

11. Porting C++/Motif app from Solaris 2.5 to SCO

12. Porting X/MOTIF App to Linux?


All times are UTC
Board index