using mySQL on a web-based server
bobs at twft.com
Mon Feb 28 19:21:09 EST 2011
Ya the "proper" way to do it is to put a server in front of the SQL and access it that way. Mind you I am currently developing an app that connects directly to an SQL database, so I'm not so proper, but I feel that the level of security to the On-Rev site, restricting connections to specific IP's and such, is going to be good enough, and the information I am putting up there is not critical or sensitive. I wouldn't recommend the approach to anyone developing apps for clients.
On Feb 28, 2011, at 3:29 PM, tkuypers at telenet.be wrote:
> Probably a stupid question, but I'm gonna post it anyway...
> I'm using a mySQL database on a server, and a livecode app which uses the info in that database.
> The mySQL is using it's default port (3306), and everything is working ok. Except with some of my bigger companies, who closed almost everything on their firewall, including (of course) port 3306 :-(
> One of the many beauties in LiveCode is it's direct access to data in a mySQL database, but what to do when this is not possible due to the above limitations?
> Do I need to create a server-side app or a webservice, which accesses the data and hands it to my apps through port 80, or are there other options?
> Mind you I know jack sh** about writing serverside apps, so any help is welcome...
> Met vriendelijke groeten,
> Ton Kuypers
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode