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
On Thu, 12 Jul 2007 21:51:27 -0400, Todd O'Bryan wrote:
> On Fri, 2007-07-13 at 01:40 +, 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
On Fri, 2007-07-13 at 01:40 +, 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
On Thu, 12 Jul 2007 20:06:33 -0500, Jeremy Dunck wrote:
> On 7/12/07, Patrick <[EMAIL PROTECTED]> wrote:
>> Using a database is assumed,
>
> Not true. URL dispatch, forms, and views still work. It very must
> depends what kind of site you're making.
>
> Though I raise my eyebrow at the idea
On 7/12/07, Patrick <[EMAIL PROTECTED]> wrote:
> Using a database is assumed,
Not true. URL dispatch, forms, and views still work.
It very must depends what kind of site you're making.
Though I raise my eyebrow at the idea that making something accessible
via web service somehow makes it more
Hi!
I'm just about to start on a project, which for security reasons might
require storing data on a separate server via undefined yet "web
services", in other words I might not be able to use a database.
I've been using Django for a couple of projects now and it transformed my
web
6 matches
Mail list logo
