Byzantium Live Distro Service Announce - Revision history

Haxwithaxe at 22:36, 9 June 2012

2012-06-09T22:36:57Z

← Older revision		Revision as of 22:36, 9 June 2012
Line 2:		Line 2:
	Share services running on a network with clients and other supernodes.		Share services running on a network with clients and other supernodes.

	Each ~~supernode (~~mesh node) maintains a ~~database~~ of all of the services and web apps it's running. That ~~database~~ is used to populate the ~~/index.php~~ page of each node. The trick lies in telling the other mesh nodes what you happen to be running and what IP address it is. This is where being able to announce what services you run to other mesh nodes will come into play.		Each mesh node maintains a list of all of the services and web apps it's running. That list is used to populate the service directory page of each node. The trick lies in telling the other mesh nodes what you happen to be running and what IP address it is. This is where being able to announce what services you run to other mesh nodes will come into play.
			We are using dns-sd via mdns/avahi/bonjour to announce services. The "__byz__._tcp" service type is being used to distribute services started by byzantium.

	This is simplified somewhat by the fact that the mesh nodes' network IP addresses are all 192.168/16.		This is simplified somewhat by the fact that the mesh nodes' network IP addresses are all 192.168/16.
Line 8:		Line 9:
	==Suggestions==		==Suggestions==
	===Contents===		===Contents===
	*~~ip address (ipv4 and/or ipv6)~~		*see dns-sd spec
	*protocol service is provided on
	**(based on name given in /etc/services maybe)
	**in services.sqlite, both tables have a field 'name' that contains the name of the service.
	*port number
	*human readable name of the service or service instance
	*human readable description of arbitrary (as much as possible) size and format
	**limit it to microblog post-~~size (140 characters)?~~
	*Put a timeout on each entry to force neighboring mesh nodes to re-poll the neighbors they know about to see if a service has been turned off by that node's admin?

	===Method===		===Method===
	*~~HTTP(S)~~		*dns-sd via mdns/bonjour/avahi
	**Use a RESTful API to make this information accessible?
	**https://~~miranda-zero.byzantium.mesh/services~~
	*socket
	*avahi?

	===Format===		===Format===
	*~~xml~~		*see dns-sd spec
	~~<pre>~~
	~~<?xml version="1.0" encoding="<encoding>" ?>~~
	~~<services>~~
	~~<service ip4="" ip6="" protocol="" port="" hr~~-~~name="" ttl="300">~~
	~~Description~~
	~~</service>~~
	~~</services>~~
	~~</pre>~~
	*delimited list
	~~<pre>~~
	~~;;;<ipv4addr>;<ipv6addr>;<protocol>;<port number>;<human readable name>;<cache TTL in seconds>;<description>~~
	~~</pre>~~

	{{Template:Byzantium}}		{{Template:Byzantium}}

ITechGeek at 09:18, 3 April 2012

2012-04-03T09:18:47Z

← Older revision		Revision as of 09:18, 3 April 2012
Line 39:		Line 39:
	;;;<ipv4addr>;<ipv6addr>;<protocol>;<port number>;<human readable name>;<cache TTL in seconds>;<description>		;;;<ipv4addr>;<ipv6addr>;<protocol>;<port number>;<human readable name>;<cache TTL in seconds>;<description>
	</pre>		</pre>

			{{Template:Byzantium}}

Drwho: /* Format */

2011-10-18T03:09:34Z

Format

← Older revision		Revision as of 03:09, 18 October 2011
Line 30:		Line 30:
	<?xml version="1.0" encoding="<encoding>" ?>		<?xml version="1.0" encoding="<encoding>" ?>
	<services>		<services>
	<service ip4="" ip6="" protocol="" port="" hr-name="">		<service ip4="" ip6="" protocol="" port="" hr-name="" ttl="300">
	Description		Description
	</service>		</service>
Line 37:		Line 37:
	*delimited list		*delimited list
	<pre>		<pre>
	;;;<ipv4addr>;<ipv6addr>;<protocol>;<port number>;<human readable name>;<description>		;;;<ipv4addr>;<ipv6addr>;<protocol>;<port number>;<human readable name>;<cache TTL in seconds>;<description>
	</pre>		</pre>

Drwho: /* Contents */

2011-10-18T03:06:54Z

Contents

← Older revision		Revision as of 03:06, 18 October 2011
Line 16:		Line 16:
	*human readable description of arbitrary (as much as possible) size and format		*human readable description of arbitrary (as much as possible) size and format
	**limit it to microblog post-size (140 characters)?		**limit it to microblog post-size (140 characters)?
			*Put a timeout on each entry to force neighboring mesh nodes to re-poll the neighbors they know about to see if a service has been turned off by that node's admin?

	===Method===		===Method===

Drwho: /* Method */

2011-10-18T03:04:55Z

Method

← Older revision		Revision as of 03:04, 18 October 2011
Line 18:		Line 18:

	===Method===		===Method===
	*~~http[s]~~		*HTTP(S)
			**Use a RESTful API to make this information accessible?
			**https://miranda-zero.byzantium.mesh/services
	*socket		*socket
			*avahi?

	===Format===		===Format===
	*xml		*xml

Drwho: /* Contents */

2011-10-18T03:01:16Z

Contents

← Older revision		Revision as of 03:01, 18 October 2011
Line 9:		Line 9:
	===Contents===		===Contents===
	*ip address (ipv4 and/or ipv6)		*ip address (ipv4 and/or ipv6)
	*protocol service is provided on (based on name given in /etc/services maybe)		*protocol service is provided on
			**(based on name given in /etc/services maybe)
			**in services.sqlite, both tables have a field 'name' that contains the name of the service.
	*port number		*port number
	*human readable name of the service or service instance		*human readable name of the service or service instance
	*human readable description of arbitrary (as much as possible) size and format		*human readable description of arbitrary (as much as possible) size and format
			**limit it to microblog post-size (140 characters)?

	===Method===		===Method===
	*http[s]		*http[s]

Drwho: /* Description */

2011-10-18T02:59:38Z

Description

← Older revision		Revision as of 02:59, 18 October 2011
Line 1:		Line 1:
	==Description==		==Description==
	Share services running on a network with clients and other supernodes.		Share services running on a network with clients and other supernodes.

			Each supernode (mesh node) maintains a database of all of the services and web apps it's running. That database is used to populate the /index.php page of each node. The trick lies in telling the other mesh nodes what you happen to be running and what IP address it is. This is where being able to announce what services you run to other mesh nodes will come into play.

			This is simplified somewhat by the fact that the mesh nodes' network IP addresses are all 192.168/16.

	==Suggestions==		==Suggestions==
	===Contents===		===Contents===

Haxwithaxe at 13:53, 1 October 2011

2011-10-01T13:53:07Z

← Older revision		Revision as of 13:53, 1 October 2011
Line 2:		Line 2:
	Share services running on a network with clients and other supernodes.		Share services running on a network with clients and other supernodes.
	==Suggestions==		==Suggestions==
	===Contents==		===Contents===
	*ip address (ipv4 and/or ipv6)		*ip address (ipv4 and/or ipv6)
	*protocol service is provided on (based on name given in /etc/services maybe)		*protocol service is provided on (based on name given in /etc/services maybe)

Haxwithaxe: Created page with "==Description== Share services running on a network with clients and other supernodes. ==Suggestions== ===Contents== ip address (ipv4 and/or ipv6) protocol service is provided ..."

2011-10-01T13:52:45Z

Created page with "==Description== Share services running on a network with clients and other supernodes. ==Suggestions== ===Contents== *ip address (ipv4 and/or ipv6) *protocol service is provided ..."

New page

==Description==
Share services running on a network with clients and other supernodes.
==Suggestions==
===Contents==
*ip address (ipv4 and/or ipv6)
*protocol service is provided on (based on name given in /etc/services maybe)
*port number
*human readable name of the service or service instance
*human readable description of arbitrary (as much as possible) size and format
===Method===
*http[s]
*socket
===Format===
*xml
<pre>
<?xml version="1.0" encoding="<encoding>" ?>
<services>
<service ip4="" ip6="" protocol="" port="" hr-name="">
Description
</service>
</services>
</pre>
*delimited list
<pre>
;;;<ipv4addr>;<ipv6addr>;<protocol>;<port number>;<human readable name>;<description>
</pre>

Byzantium Live Distro Service Announce - Revision history

Haxwithaxe at 22:36, 9 June 2012

ITechGeek at 09:18, 3 April 2012

Drwho: /* Format */

Drwho: /* Contents */

Drwho: /* Method */

Drwho: /* Contents */

Drwho: /* Description */

Haxwithaxe at 13:53, 1 October 2011

Haxwithaxe: Created page with "==Description== Share services running on a network with clients and other supernodes. ==Suggestions== ===Contents== *ip address (ipv4 and/or ipv6) *protocol service is provided ..."

Haxwithaxe: Created page with "==Description== Share services running on a network with clients and other supernodes. ==Suggestions== ===Contents== ip address (ipv4 and/or ipv6) protocol service is provided ..."