I've done a lot of applications with this kind of concern. But it really doesn't change the design much. The web server goes on one side of the DMZ and the database server goes on the other. That probably should be the standard anyway, keep as little extraneous data as possible on the web server. Works very well and is about as secure as you are going to get. If "they" can crack your database, I would bet "they" will be able to crack your web service.
On 7/12/07, Patrick <[EMAIL PROTECTED]> wrote: > > > Unfortunately, I can't give you more details about the security aspect, > except that it has to do with prolonged physical storage of large amounts > of data online, which is "insecure". The exact details are not known to > me yet. I'm a developer that has been told to make a web app instead of a > desktop program that works with a pretty old system :) > > I know it sounds a bit contradictory, but at this point I'm exploring > possibilities. It might be that a database would be the best option in > the end. It would be so much easier. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
