ESAPI Framework Strategy - Revision history

Monzillo at 14:47, 11 December 2008

2008-12-11T14:47:18Z

Monzillo at 14:46, 11 December 2008

2008-12-11T14:46:02Z

Monzillo: New page: the esapi should be defined such that it can be used on behalf of applications by frameworks including containers (unless the nature of the functionality is such that it can only work fro...

2008-12-11T14:40:13Z

New page: the esapi should be defined such that it can be used on behalf of applications by frameworks including containers (unless the nature of the functionality is such that it can only work fro...

New page

the esapi should

be defined such that it can be used on behalf of applications by frameworks including containers (unless the nature of the functionality is such that it can only work from the application). another way this was said, is such that the api is compatible with ioc.

share the representations of authentication state employed by the underlying framework or runtime environment.

leverage the access control primitives (e.j. Java permissions) employed by the underlying framework or runtime environment

← Older revision		Revision as of 14:47, 11 December 2008
Line 7:		Line 7:
	leverage the access control primitives (e.j. Java permissions) employed by the underlying framework or runtime environment		leverage the access control primitives (e.j. Java permissions) employed by the underlying framework or runtime environment

−	where api must be embedded in app, consider separation of the specification of the logical effect of what must be ~~achived~~ (in the app) from the details of how it will be accomplished, such that different mechanisms can be bound to achieve the effect, such as the case with Java Annotations.	+	where the api must be embedded in the app, consider separation of the specification of the logical effect of what must be achieved (in the app) from the details of how it will be accomplished, such that different mechanisms can be bound to achieve the effect, such as the case with Java Annotations.

← Older revision		Revision as of 14:46, 11 December 2008
Line 6:		Line 6:

	leverage the access control primitives (e.j. Java permissions) employed by the underlying framework or runtime environment		leverage the access control primitives (e.j. Java permissions) employed by the underlying framework or runtime environment
		+
		+	where api must be embedded in app, consider separation of the specification of the logical effect of what must be achived (in the app) from the details of how it will be accomplished, such that different mechanisms can be bound to achieve the effect, such as the case with Java Annotations.