Jeff Williams wrote...
> I think we're focused on different aspects of 'important.'
> The sheer number of web applications does make concurrency
> in that environment an important issue for this list.
> Concurrency used to be the province of a relatively
> small number of developers who understo
At 9:03 AM -0500 2/2/05, Jeff Williams wrote:
>I think we're focused on different aspects of 'important.' The sheer number of
>web applications does make concurrency in that environment an important issue
>for this list.
Certainly I have no object to the notion that concurrency is important for
portant'.
--Jeff
- Original Message -
From: "ljknews" <[EMAIL PROTECTED]>
To: "Secure Coding Mailing List"
Sent: Tuesday, February 01, 2005 6:50 PM
Subject: Re: [SC-L] free lunch almost over
At 6:14 PM -0500 2/1/05, Jeff Williams wrote:
Sure. How many of those
on Tuesday February 1, 2005, Jeff Williams wrote:
> >> Concurrency is a huge issue and nowhere more important than web
> >> applications.
> >
> > Ummm... How about realtime fly-by-wire control systems ?
> > --
> > Larry Kilgallen
>
> Sure. How many of those are there?
I am certainly no
At 6:14 PM -0500 2/1/05, Jeff Williams wrote:
>Sure. How many of those are there?
>
>--Jeff
>
>- Original Message - From: "ljknews" <[EMAIL PROTECTED]>
>To: "Secure Coding Mailing List"
>Sent: Tuesday, February 01, 2005 4:11 PM
>Subject: R
Sure. How many of those are there?
--Jeff
- Original Message -
From: "ljknews" <[EMAIL PROTECTED]>
To: "Secure Coding Mailing List"
Sent: Tuesday, February 01, 2005 4:11 PM
Subject: Re: [SC-L] free lunch almost over
At 3:23 PM -0500 2/1/05, Jeff Williams wr
At 3:23 PM -0500 2/1/05, Jeff Williams wrote:
> Concurrency is a huge issue and nowhere more important than web applications.
Ummm... How about realtime fly-by-wire control systems ?
--
Larry Kilgallen
In message <[EMAIL PROTECTED]>, Gunnar Peterson
writes:
>If you do the math on what comes next after the processor
>manufacturers' free lunch is over, the implications to concurrency,
>security, and privacy are huge:
>
>http://www.gotw.ca/publications/concurrency-ddj.htm
>
>How do traditional se
Agree. Also, the author's conclusion that:
"Efficiency and performance optimization will get more, not less,
important"
Security is already viewed as an obstacle to the above factors. Couple
that with the inherent complexity in concurrent programming models, and
you get three of security's arch
appened to report it.
If you're interested, there's a lesson in WebGoat at OWASP that teaches
developers about these flaws and how to avoid them.
--Jeff
- Original Message -
From: "Gunnar Peterson" <[EMAIL PROTECTED]>
To: "Secure Coding Mailing List"
If you do the math on what comes next after the processor
manufacturers' free lunch is over, the implications to concurrency,
security, and privacy are huge:
http://www.gotw.ca/publications/concurrency-ddj.htm
How do traditional security mechanisms function in a massively
concurrent world? How
11 matches
Mail list logo
