Protocols

From The Socknet

Note: Protocol documents are not part of the Socknet specification.

A Socknet provider can store connection information on registered services in order to facilitate their interaction.

A protocol is identified by a string that SHOULD be a URL which SHOULD have human-readable documentation for the protocol.

There is currently no repository of links to known protocols.

Aside from storing service data, providers do not need to deal with protocols directly. That is, a Socknet provider has no need to understand the RSS2 protocol, for example. (Although, that particular protocol is highly suggested.)

Considerations

Providers may access the services' protocol information in order to enhance the user experience too. That's just not the main objective.

Protocol names are URL's in order to avoid clashes in protocol names and to assist with the dissemination of information about protocols.

Nothing bars a provider from providing services as well.