On Thu, 12 Jul 2007 21:51:27 -0400, Todd O'Bryan wrote: > On Fri, 2007-07-13 at 01:40 +0000, Patrick 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. > > What if you mocked up your own backend to connect to whatever storage > solution they have in mind. You could use models internally and only > have to worry about storing and retrieving. Also, chances are that you > wouldn't have to implement all the bells and whistles of the other > backends but could get by with a subset based on what you're accessing > and storing. > >
I guess I could use models internally, though the problem I would have to worry about is storing and retrieving data remotely, though I'm beginning to think that it's probably possible and actually might be the simplest and preffered thing is to use one of the database backends that Django supports on the server that I would connect to via "web services", which should be as "secure," if not more so. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
