I'm just starting a new, 'simple' project. It must permit a degree of CRUD with an existing Access database, heavily endowed with expensive office apps, while offering a public internet front end.
Having just finished one large project with cake (univerd.com), and also being halfway through another hosted on a stick, I'd quite like to continue the theme. I spent all morning reading up on XML & SOAP and then turned up this statement: (google the sentence and you'll find the page) "SOAP and WSDL are going the way of the dodo, fortunately. The enterprisey world is buzzing with REST" Now I'm beginning to wonder if I'm approaching this right. At the moment we have two possible approaches...maybe three. preferred: Run the whole www show from MySql, synchronising with the Access db on a 12 or 24 hour cron. The Access db would be retained for office use. soapy: Maintain a live link between the two dbs using SOAP or other Web Services technology outside chance - depends on 3rd party cooperation: Migrate the Access db to MySql and front that in the office with the Access clients/apps. Don't know if they'll work over the outernet. Anybody have any ideas on this? A few years ago I worked on a similar project aiming to keep two dissimilar systems (a CAD and a GIS) in sync. Disaster. Walking away is not an option. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
