PHP is good for server-side and there are frameworks that will help you encapsulate database layer so you can easily switch from one db engine to another e.g. MySQL to PGSQL,etc.
Built in PHP is PHP Data objects library that can help you with this problem as well if you need a thin layer for your database layer. JC --- In [email protected], "raja_s_patil" <kpr.rspa...@...> wrote: > > Hello, > > We are in process of converting a Desktop C/S Database application > to web application. Till date we have not developed any web > application. We have evaluated Flex as development platform > and created a small pilot application without data access > and the respective client has admired general features provided > by Flex. Now we would like to evaluate data access part of Flex. > > Now what we need is help on designing data access part of > application. Since this is First Adventure for Both of us > (Client and We) there is no legacy system so we are starting > from scratch. Can somebody suggest how we should proceed so > that there are no/minimum problem in production. At present > the application being ported to we is written in Delphi with > Firebird as Database Engine. Most of the business logic is > stored in Stored Procedures and runs on Linux, Win XP, Win 98 as > data base servers. We dont mind on time to be taken for development > or efforts in developing/implementing but we expect to achieve > following goals. > > 1> The application should be independent of Backend database. > i.e. it should be able to use any of Oracle, MS-SQL, MySQL, > PostgreSQL, Firebird as backend. > 2> The business logic should move from Stored procedures to some > middle layer i.e. to Application server. > 3> It should be possible to separate application server and database > server i.e. application server and Database servers can be at > different physical locations or they can reside on same server. > 4> the communication between database server->application server and > application Server->Client should be secured one or may be > encrypted so that man in middle is not able to modify the data > > To best of our knowledge we have got a rough layout as follows. > To start with have spring as application server with hibernate > integration for data access. Then Flex application will > communicate with application server through BlazeDS. > > Can somebody suggest us a better way of doing it so that > above goals are achieved and efforts are minimised for both > development/implementation and maintenance. > > Thanks for reading this long post and best regards > > raja >
