Directional Advice Sockets, Server?

[cph]

I'm new to livecode and I guess the compelling reason to use it for development is livecode's cross platform capabilities as well as the speed of development.

We have an immediate need to develop a business application which will evolve over time to many modules. We currently use postgres for extensive reporting using Birt so have experience and a preference for postgres. Essentially we want to develop a desktop app accessing our postgress db on a linux server.

Having spent hours reading through the options like using sockets or using the livecode server etc I still really don't know the best option. The application we will develop could potentially have over 200 users with 50% concurrently processing transactional data on the db during peak times.

I'm sure there are some very smart livecode developers out there who can point us in the right direction.

Thanks in anticipation of your help.

[bangkok]

app clients and the linux server are on the same local network ?

if yes :
-no need socket. the app clients can connect directly to the postgresql server. Livecode has a driver for postgresql.
However, with a MS SQL server then the socket server is an interesting solution, because no need to set up an odbc DSN on each client PC. easier and more secure.

if no :
-no need socket. use instead a livecode server, installed on your linux server, that will receive queries through web queries (POST) and forward them to the postgresql server.

[cph]

Thanks bangkok, the app clients will be on a different network so we will pursue the livecode server option. Appreciate your advice.

Regards, Chris

[mwieder]

Chris-

It *is* possible to do this without the liveserver component by putting together a small stack the uses talks to the postgres database and sockets to communicate with the client apps, or by setting up web services on the server, but probably going the liveserver route is a better route for what you have in mind.