For issue #1 :
This really depends on your application. If all the intermediary is doing is repackaging a mySQL response (i.e. no processing to speak of), going directly to an SQL connection will be speedier with less overhead (XML processing, by and large, is slow). If you envision that the data source may, at some point, be externalized, going with Web-Services like you do might be preferrable, since you'll be able to more easily write wrappers.
If "all" that the backend server is doing is holding data, then running just mySQL and giving it as many resources as possible with as few context switches as possible is, IMHO, a better use of resources than running a complete Web server stack on the same machine, as well.
#2 :
This depends again on how you currently implement authentication :-) Sure it's possible to stip digest authentication based on source addresses. (On Apache, the Satisfy directive (http://httpd.apache.org/d
I'm wondering though ... since you use CURL to query data from backend-servers -- are those backend-server enduser-visible ? If so, why ?
Main Topics
Browse All Topics





by: periwinklePosted on 2006-09-22 at 14:56:11ID: 17581050
Might it make more sense to password protect using MySQL database table? Then you could just access the appropriate server, and keep records of who is logged in, and the time they last accessed the site (so that you could tell if the login had expired)?