|
> From: SCarter@rsrcorp.com > > OK I think I have been severely scolded by now.... I'm not scolding, just pointing out something you might want to consider. > I think Joe was talking about creating my own server, how would > we go about > doing this? This depends on the amount of work you want to do. A relatively simple messaging protocol is not hard to implement, but you will have to write a database server for each set of related files you wish to expose. It's not difficult, but it can be a lot of code. > I have looked into Scott Klements socket programming site is this what you > are talking about? > http://klement.dstorm.net/rpg/socktut/ > > If so (and I have not looked at the whole thing) how would this be > different than opening acces to ODBC? The difference is that you would have your own protocol, so a hacker is less likely to be able to figure out how to access your data. Every two-bit script kiddie on the planet knows how to DELETE FROM TABLE, but they wouldn't know your particular messaging protocol. As Leif points out, though, you may still want to put an encryption algorithm on top of your messaging protocol.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.