URI Schema » History » Version 42

« Previous - Version 42/59 (diff) - Next » - Current version
J. Wienke, 05/12/2011 11:23 AM
tried to clean up old mess (still available in history) and condense the rationales discussed there


URI Schema

URI types

Generic:
rsb:///hierarchical/service/definition/further/to/participant

This may resolve to:
  • Service and/or Participant
    • If there is only one of these entities this is enough for resolving it
    • If multiple entities reside on this scope, a single instance can be selected using their UUID.
      rsb:///hierarchical/service/definition/further/to/participant#UniqueIDOfParticipant [UUID]
  • Nothing ;)

These generic URIs require a global naming service.

Specific:

transport://<location.transport.specific[:PORT]>/hierarchical/service/definition/further/to/participant

Location uniquely identifies a single participant or service, hence an ID part is not required any more.

Specific IDs can be resolved by the respective connectors and do not require a global naming.

Rationale

  • generic: usually location transparency should be available
  • specific: specific access without naming
  • UUIDs should ideally not be required to keep URIs simple