tim11 at bellatlantic.net
Tue Sep 3 18:23:01 CDT 2002
On 9/3/02 11:44 AM, "Jerry Daniels" <Jedaniels at evercom.net> wrote:
> Why not try using a three-tier architecture? Apache, PHP and MySQL? That way
> the database access is still local and web browsers could also access the
> data. You could use XML for the Apache-to-Rev return data, perhaps.
> Just an idea.
> -----Original Message-----
> From: Tim [mailto:tim11 at bellatlantic.net]
> Sent: Monday, September 02, 2002 2:53 PM
> To: use-revolution at lists.runrev.com
> Subject: Re: Database question
> On 9/2/02 1:28 PM, "Tuviah M Snyder" <diskot123 at juno.com> wrote:
>> Try prohosting (www.prohosting.com). They offer inexpensive mysql, php,
>> and webhosting. You can access the mysql database remotely from any
>> system, I use it myself to test mysql access.
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
> Thank you Tuviah. It looks like I'll be switching my ISP for the second time
> this year. Just out of curiosity, is it feasible to set up MYSQL in such a
> way as to have it accessed by remote clients (like Rev) and having
> permissions granted for every client (thus according to some ISP's, opening
> doors to hackers), or was MYSQL designed more for being accessed locally?
> I'm just trying to figure out the workflow, whether the Rev client should
> access the data remotely or communicate with a local version of itself
> already on the server?
That seems to be the way to go. Accessing MYSQL remotely is more of a hassle
than it seems.
More information about the use-livecode