Ticket #6 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

Resource resolution via URIs

Reported by: shane Assigned to: shane
Priority: high Milestone: 1.0a1
Component: uriResolver Version: 1.0
Severity: new item Keywords: uri
Cc:

Description (Last modified by shane)

Some thought should be put into how to specify and work with URIs for skins and resources they reference. Resource references should be able to be relative or absolute and general conformance with HTML and XML rules should be kept.

See Uniform Resource Identifiers (URI): Generic Syntax for additional reference, as well as our uriParser module.

Change History

07/27/04 23:42:48 changed by shane

  • description changed.

08/07/04 00:15:24 changed by shane

  • status changed from new to assigned.

08/10/04 00:29:23 changed by shane

  • severity changed from critical to new item.

08/31/04 00:27:37 changed by shane

  • keywords set to uri.

Progress has been made! See changesets [237], [235], [233], [232], [231], and [229].

Work remaining:

  • Have a resolver composition that automatically resolves zip files on path
  • Switch skinning's current resolvers for uriResolvers.

09/01/04 01:17:55 changed by shane

Changesets [238] and [239] were added for this ticket. Expect integration between skinning and uriResolvers soon.

09/02/04 00:32:32 changed by shane

  • status changed from assigned to closed.
  • component changed from skinning (framework) to uriResolver.
  • resolution set to fixed.

Creating a Resolver that automatically detects file containers (like Zip) when they are present in the path has been seperated into ticket #24.

Integration of uriResolver and skinning frameworks was committed in changeset [240], resolving this ticket.