Depending on the client we wrote the middle ware ourselves. Will the sql request be different everytime?
-----Original Message----- From: "Rob" <[EMAIL PROTECTED]> To: "REALbasic NUG" <[email protected]> Sent: 1/12/2007 1:12 PM Subject: Re: Converting desktop app to multi-user "Smart Client" Giovanni, The data isn't that time sensitive (I don't need real-time data) so it shouldn't be a problem. I'm thinking a sync operation every 5min or so. What method did you choose to transfer the data? did you sent the entire sql command? Also, did you write your own middleware tier or use an existing library? Thanks, Rob ----- Original Message ----- From: "Giovanni" <[EMAIL PROTECTED]> To: "REALbasic NUG" <[email protected]> Sent: Friday, January 12, 2007 3:52 PM Subject: RE: Converting desktop app to multi-user "Smart Client" You can create a php tier connection to your mysql. It works but there is a speed penalty which may not be too bad. We have used this method whenever a client could not connect or wouldn't want a direct connection due to security. As a matter of fact you can even encrypt the page... -----Original Message----- From: "Rob" <[EMAIL PROTECTED]> To: "REALbasic NUG" <[email protected]> Sent: 1/12/2007 12:14 PM Subject: Re: Converting desktop app to multi-user "Smart Client" Adam, Unfortunately our server setup does not allow direct access to MySQL from remote machines so there will have to be another tier. I've tried in the past to use RB as a CGI on the server but it doesn't work with my versions of Debian and Apache. Rob ----- Original Message ----- From: "Adam Shirey" <[EMAIL PROTECTED]> To: "REALbasic NUG" <[email protected]> Sent: Friday, January 12, 2007 3:00 PM Subject: Re: Converting desktop app to multi-user "Smart Client" > Rob, > > If it's all one client (but with an online and an offline mode), why not > connect to your MySQL alongside your REALSQLDatabase? Then it's basically > copying data from one DB to another: Select data from your REAL db where > the > record is dirty, and for every record, update or insert the record into > the > MySQL db. > > > -Adam > > > On 1/12/07, Rob <[EMAIL PROTECTED]> wrote: >> >> Hi Adam, >> Yes, the 'offline' clients are using realSQL databases with an identical >> schema. >> That's essentially what I was doing for the local version, using standard >> sqlexecute and db records to insert, add, update etc. to the realSQL db. >> My >> thought was then to query the realSQL for records where 'to update'= true >> then generate the commands to update the server (sending them through an >> httpsocket). >> >> Any thoughts on how to transmit the data? I was thinking the most secure >> way >> would be to generate an http post with the command type (1 for add, 2 for >> delete, etc.) and adding the parameters as part of the post. >> Something like server.php >> ?1&username&password&tablename&John&Smith&555-1212 >> Then have the php assemble the sql. >> >> Thanks, >> Rob >> >> >> ----- Original Message ----- >> From: "Adam Shirey" <[EMAIL PROTECTED]> >> To: "REALbasic NUG" <[email protected]> >> Sent: Friday, January 12, 2007 1:08 PM >> Subject: Re: Converting desktop app to multi-user "Smart Client" >> >> >> > Hi Rob, >> > >> > I assume that for 'offline' mode, you'll have a reliable method for >> > storing >> > data -- perhaps a REALSQLDatabase of the same schema as the server so >> you >> > can run queries and store data to be synchronized? The first instinct >> > seems >> > to be to do this so offline clients can insert data that can be easily >> > queried and manipulated; then, when you sync up, you can have a >> > function >> > that finds everything with its dirty bit set, assembles SQL queries, >> > and >> > executes them. >> > >> > Easier yet, create one DatabaseRecord for each dirty object and insert >> > it -- >> > no SQL query required, and it can be BLOB-friendly. >> > >> > Knowing a little more of your implementation may help with suggestions >> for >> > your implementation. >> > >> > >> > HTH! >> > -Adam >> > >> > On 1/12/07, Rob <[EMAIL PROTECTED]> wrote: >> >> >> >> Hi all, >> >> I have created a desktop database front end to handle some of our >> >> company's >> >> workflow processes. We are now hoping to modify the app so individual >> >> users >> >> can run the app on there local machine (both on and off line) and sync >> >> data >> >> to a central server. >> >> The server will most likely be a Linux box using php as middleware and >> >> MySQL >> >> as a database. The system will have approx. 20-30 unique users who >> >> will >> >> have >> >> different levels of access (controlled by the database.) >> >> >> >> In planning for this upgrade I have identified 2 potential issues; >> >> >> >> 1) determining best way to handle local to network data sync. >> >> I will be creating a UUID for each record so I'm not worried about >> >> duplicate >> >> record ID's. What does concern me is how to determine what records >> >> need >> >> to >> >> be synced. The only thing I can think of is to have a "last mo [truncated by sender] _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
