OhNet:What - Revision history

Keith at 11:21, 10 October 2011

2011-10-10T11:21:34Z

← Older revision		Revision as of 11:21, 10 October 2011
Line 1:		Line 1:
	{{nav_openhome_ohnet\|ohNet - What is it?}}		{{nav_openhome_ohnet\|ohNet - What is it?}}
-	ohNet is a modern~~, thoughtfully architected~~, cross platform, UPnP stack. ohNet includes both ~~full~~ control point and device ~~stacks~~ that can be used together or independently. It runs on Linux, Windows, Mac, iOS and Android. The public APIs are available for the device and control point stacks in C++, C#, Java, C. There is an JavaScript api for the control point stack.	+	ohNet is a modern, cross platform UPnP stack. ohNet includes both a control point and a device stack that can be used together or independently. It runs on Linux, Windows, Mac, iOS and Android. The public APIs are available for the device and control point stacks in C++, C#, Java, C. There is an JavaScript api for the control point stack.

	UPnP services are presented as classes with actions appearing as functions and state variables appearing as member variables. These classes are referred to as proxies for users of the control point stack and providers for users of the device stack.		UPnP services are presented as classes with actions appearing as functions and state variables appearing as member variables. These classes are referred to as proxies for users of the control point stack and providers for users of the device stack.

Keith at 11:19, 10 October 2011

2011-10-10T11:19:57Z

← Older revision		Revision as of 11:19, 10 October 2011
Line 1:		Line 1:
	{{nav_openhome_ohnet\|ohNet - What is it?}}		{{nav_openhome_ohnet\|ohNet - What is it?}}
-	ohNet is a ~~full~~ UPnP stack. ~~Ports exist for~~ Linux, Windows, Mac, iOS and Android. The public APIs are ~~protocol independent~~ and ~~offered~~ in C++, C#, Java, C ~~and~~ JavaScript ~~(Control Point only)~~.	+	ohNet is a modern, thoughtfully architected, cross platform, UPnP stack. ohNet includes both full control point and device stacks that can be used together or independently. It runs on Linux, Windows, Mac, iOS and Android. The public APIs are available for the device and control point stacks in C++, C#, Java, C. There is an JavaScript api for the control point stack.

-	UPnP services are presented as classes with actions appearing as functions and state variables appearing as member variables. These classes are referred to as proxies for users of the ~~Control Point~~ stack and providers for users of the ~~Device~~ stack.	+	UPnP services are presented as classes with actions appearing as functions and state variables appearing as member variables. These classes are referred to as proxies for users of the control point stack and providers for users of the device stack.

	Proxies and Providers are included for all OpenHome and UPnP AV services. If your application uses other services, ohNet includes a tool (ohNetGen) to generate proxies and/or providers from the service XML in any of the supported languages.		Proxies and Providers are included for all OpenHome and UPnP AV services. If your application uses other services, ohNet includes a tool (ohNetGen) to generate proxies and/or providers from the service XML in any of the supported languages.

	Source code is available under a Simplified BSD license.		Source code is available under a Simplified BSD license.

Simonc at 14:17, 2 September 2011

2011-09-02T14:17:16Z

← Older revision		Revision as of 14:17, 2 September 2011
Line 1:		Line 1:
	{{nav_openhome_ohnet\|ohNet - What is it?}}		{{nav_openhome_ohnet\|ohNet - What is it?}}
-	ohNet is a full UPnP stack. Ports exist for Linux ~~and~~ Windows (Mac ~~is in progress)~~. The public APIs are protocol independent and offered in C++, C#, Java, C and JavaScript (Control Point only).	+	ohNet is a full UPnP stack. Ports exist for Linux, Windows, Mac, iOS and Android. The public APIs are protocol independent and offered in C++, C#, Java, C and JavaScript (Control Point only).

	UPnP services are presented as classes with actions appearing as functions and state variables appearing as member variables. These classes are referred to as proxies for users of the Control Point stack and providers for users of the Device stack.		UPnP services are presented as classes with actions appearing as functions and state variables appearing as member variables. These classes are referred to as proxies for users of the Control Point stack and providers for users of the Device stack.

	Proxies and Providers are included for all OpenHome and UPnP AV services. If your application uses other services, ohNet includes a tool (ohNetGen) to generate proxies and/or providers from the service XML in any of the supported languages.		Proxies and Providers are included for all OpenHome and UPnP AV services. If your application uses other services, ohNet includes a tool (ohNetGen) to generate proxies and/or providers from the service XML in any of the supported languages.
		+
		+	Source code is available under a Simplified BSD license.

Simonc at 16:04, 2 August 2011

2011-08-02T16:04:18Z

← Older revision		Revision as of 16:04, 2 August 2011
Line 1:		Line 1:
-	{{nav_openhome_ohnet\|~~OpenHome Net~~ - What is it?}}	+	{{nav_openhome_ohnet\|ohNet - What is it?}}
	ohNet is a full UPnP stack. Ports exist for Linux and Windows (Mac is in progress). The public APIs are protocol independent and offered in C++, C#, Java, C and JavaScript (Control Point only).		ohNet is a full UPnP stack. Ports exist for Linux and Windows (Mac is in progress). The public APIs are protocol independent and offered in C++, C#, Java, C and JavaScript (Control Point only).

Simonc at 16:00, 2 August 2011

2011-08-02T16:00:46Z

← Older revision		Revision as of 16:00, 2 August 2011
Line 1:		Line 1:
	{{nav_openhome_ohnet\|OpenHome Net - What is it?}}		{{nav_openhome_ohnet\|OpenHome Net - What is it?}}
-	ohNet is a full UPnP stack. Ports exist for Linux and Windows (Mac is in progress). The public APIs are protocol independent and offered in C++, C#, C and JavaScript (Control Point only).	+	ohNet is a full UPnP stack. Ports exist for Linux and Windows (Mac is in progress). The public APIs are protocol independent and offered in C++, C#, Java, C and JavaScript (Control Point only).

	UPnP services are presented as classes with actions appearing as functions and state variables appearing as member variables. These classes are referred to as proxies for users of the Control Point stack and providers for users of the Device stack.		UPnP services are presented as classes with actions appearing as functions and state variables appearing as member variables. These classes are referred to as proxies for users of the Control Point stack and providers for users of the Device stack.

	Proxies and Providers are included for all OpenHome and UPnP AV services. If your application uses other services, ohNet includes a tool (ohNetGen) to generate proxies and/or providers from the service XML in any of the supported languages.		Proxies and Providers are included for all OpenHome and UPnP AV services. If your application uses other services, ohNet includes a tool (ohNetGen) to generate proxies and/or providers from the service XML in any of the supported languages.

Openhome at 09:46, 1 August 2011

2011-08-01T09:46:48Z

← Older revision		Revision as of 09:46, 1 August 2011
Line 1:		Line 1:
-	{{nav_openhome_ohnet\|~~ohNet~~ - What is it?}}	+	{{nav_openhome_ohnet\|OpenHome Net - What is it?}}
	ohNet is a full UPnP stack. Ports exist for Linux and Windows (Mac is in progress). The public APIs are protocol independent and offered in C++, C#, C and JavaScript (Control Point only).		ohNet is a full UPnP stack. Ports exist for Linux and Windows (Mac is in progress). The public APIs are protocol independent and offered in C++, C#, C and JavaScript (Control Point only).

Openhome: moved OhNet-What to OhNet:What

2011-08-01T09:32:31Z

moved OhNet-What to OhNet:What

← Older revision

Revision as of 09:32, 1 August 2011

Keith at 14:20, 6 July 2011

2011-07-06T14:20:28Z

← Older revision		Revision as of 14:20, 6 July 2011
Line 4:		Line 4:
	UPnP services are presented as classes with actions appearing as functions and state variables appearing as member variables. These classes are referred to as proxies for users of the Control Point stack and providers for users of the Device stack.		UPnP services are presented as classes with actions appearing as functions and state variables appearing as member variables. These classes are referred to as proxies for users of the Control Point stack and providers for users of the Device stack.

-	Proxies and Providers are included for all OpenHome ~~Media~~ and UPnP AV services. If your application uses other services, ohNet includes a tool (ohNetGen) to generate proxies and/or providers from the service XML in any of the supported languages.	+	Proxies and Providers are included for all OpenHome and UPnP AV services. If your application uses other services, ohNet includes a tool (ohNetGen) to generate proxies and/or providers from the service XML in any of the supported languages.

Keith at 14:20, 6 July 2011

2011-07-06T14:20:20Z

← Older revision		Revision as of 14:20, 6 July 2011
Line 4:		Line 4:
	UPnP services are presented as classes with actions appearing as functions and state variables appearing as member variables. These classes are referred to as proxies for users of the Control Point stack and providers for users of the Device stack.		UPnP services are presented as classes with actions appearing as functions and state variables appearing as member variables. These classes are referred to as proxies for users of the Control Point stack and providers for users of the Device stack.

-	Proxies and Providers are included for all OpenHome and UPnP AV services. If your application uses other services, ohNet includes a tool (ohNetGen) to generate proxies and/or providers from the service XML in any of the supported languages.	+	Proxies and Providers are included for all OpenHome Media and UPnP AV services. If your application uses other services, ohNet includes a tool (ohNetGen) to generate proxies and/or providers from the service XML in any of the supported languages.

Simonc at 15:08, 4 July 2011

2011-07-04T15:08:48Z

← Older revision		Revision as of 15:08, 4 July 2011
Line 1:		Line 1:
-	{{nav_openhome_ohnet\|~~OpenHome~~ ohNet - What is it?}}	+	{{nav_openhome_ohnet\|ohNet - What is it?}}
	ohNet is a full UPnP stack. Ports exist for Linux and Windows (Mac is in progress). The public APIs are protocol independent and offered in C++, C#, C and JavaScript (Control Point only).		ohNet is a full UPnP stack. Ports exist for Linux and Windows (Mac is in progress). The public APIs are protocol independent and offered in C++, C#, C and JavaScript (Control Point only).