Special

Clearance Sale!

We've been publishing for over five years now and it's time to clear out our inventory of back issues, so we're slashing prices!

RBD Magazines

Check out this amazing clearance sale of all our past issues. Missing some issues? This is a great time to complete your RBD collection. Save up to 40% off the regular price of our printed back issue packages. These prices are only good until the end of the year May 2008 and supplies are limited, so place your order today.

Article Preview


Buy Now

Print:
PDF:

Beyond the Limits

Talking to remote databases

Issue: 2.4 (March/April 2004)
Author: Didier Barbas
Author Bio: Didier has been a dilettante programmer and linguist for more than 20 years. Unusual for a Frenchman, he speaks 11 languages, including Korean and PowerPC machine language.
Article Description: No description available.
Article Length (in bytes): 7,087
Starting Page Number: 46
RBD Number: 2423
Resource File(s):

Download Icon 2423.sit Updated: Monday, March 15, 2004 at 1:02 AM

Related Link(s): None
Known Limitations: None

Excerpt of article text...

With blog-mania in full swing these days, there are many blog owners who have their domain set up on a Unix-like server (Apache, PHP, MySQL on RedHat, etc. -- does this sound familiar?) that doesn't allow remote connections to the MySQL server: all accesses have to be done locally, via PHP, Perl, or Python scripts to name a few. But what if we'd like to write our own blog system, complete with posting and archiving software (in RB, of course)? The short answer would be, "Geez, I'm stuck!" A longer answer is: Well, there is a way, but we will need more than just RB. Here's how.

We need a friend!

Since our hypothetical but oh-so-common MySQL server will not accept requests from us, we need to arrange a third party, hosted on the server, that will accept and forward them to the server. There are several issues here: one is security, obviously. What do we allow to be forwarded, and what do we not? How do we restrict access to that third party?

Another one is the "grammar" of the requests: do we accept them "as is" and pass them on? Do we encrypt them? Do we split the "third party" into several scripts, each accepting only one kind of request (e.g., POST = INSERT/UPDATE; GET = SELECT)?

...End of Excerpt. Please purchase the magazine to read the full article.

Article copyrighted by REALbasic Developer magazine. All rights reserved.


 


|

 


Weblog Commenting and Trackback by HaloScan.com