Re: Mysql over HTTP
"Daniel da Veiga" <[email protected]>
| Newsgroups | gmane.comp.db.mysql.windows |
|---|---|
| Message-ID | <[email protected]> |
On 4/7/06, Jangita <[email protected]> wrote: > Hi all, > > It's all well and good having mysql using port 3309 (or any other port for > that matter); I'm writing an application that will be used by loads of users > off the internet - so I'm expecting firewall issues. > > One easy way is to have the mysql traffic flow over port 80; that works > sometimes but not with intelligent firewalls that only allow http traffic or > companies that have only http ports open (yes there are many of these) > > One method I've thought about that goes around this is to write an interface > that sits in-front of the mysql client and translates the mysql traffic into > http get or put requests and use wininet.dll to send these requests to the > server. Since these are get and put requests I'll have to write and install > a cgi or isapi dll on the webserver which translates these requests into > normal traffic and relays it to the mysql server and vice versa. > > This would in effect produce an environment where as long as you can browse > you can use the mysql client application (with iexplore because of wininet) > - and with linux to some extent and this will also be able to go thru http > proxies etc (basically anything that ie can go thru) > > Before I get my hands dirty; is there anything like this that exists out > there? I have a week leave from Monday and if there isn't well im about to > start writing one. > Is there any specific reason for you not to write your application using a web language like PHP, Perl, ASP, .NET or anything like that? You mentioned some weird convertions regarding TCP packages headers and filtering, while searching for a solution to let an app access MySQL trough firewalls and/or proxies, why not simply write a CGI or server-side based app? You'll have LOTS of problems while dealing with TCP/IP packaging and headers and converting it all to HTTP traffic, besides, you'll probably load your server a LOT while still having to write a client-side AND a server-side conversion tool for traffic. Besides, it won't be fail proof as you can still step in some routers that may block your converted packages. If you want to use a browser-like app, why not let the browser do its work? -- Daniel da Veiga Computer Operator - RS - Brazil -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ ------END GEEK CODE BLOCK------ -- MySQL Windows Mailing List For list archives: http://lists.mysql.com/win32 To unsubscribe: http://lists.mysql.com/[email protected]