Channel - Revision history

D.franco: /* {{VULCON}} / {{GVCONSOLE}} Configuration */

2013-07-31T08:32:59Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

2013-02-27T11:30:40Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

2013-02-27T11:28:08Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

2013-02-27T11:25:31Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

2013-02-27T11:25:07Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

2013-02-27T11:24:24Z

2013-02-27T10:53:41Z

‎Description

2013-02-27T10:53:28Z

‎Description

2013-02-27T10:53:11Z

‎Description

2013-02-26T16:18:21Z

‎Description

@@ Line 9: / Line 9: @@
 =={{VULCON}} / {{GVCONSOLE}} Configuration==
-The Channel is identified by an unique attribute id-channel, this attribute is unique within the System entity.The Channel subelement are the Operations, {{GVESB}} offers a wide variety of Operations that you can use in your service. See [[plugins]] section.
+The Channel is identified by an unique attribute id-channel, this attribute is unique within the System entity. The Channel subelement are the Operations, {{GVESB}} offers a wide variety of Operations that you can use in your service. See [[plugins]] section.
 ==How To==
 From the {{L_VULCON}} Core view, it is possible to insert a new Channel by right clicking the [[System]] element you are working on. Then ''Insert after'' and press Channel*. A new Channel element will be created. Fill the ''id-channel'' property in the properties view. Now you can insert all the operations needed.

@@ Line 10: / Line 10: @@
 The Channel is identified by an unique attribute id-channel, this attribute is unique within the System entity.The Channel subelement are the Operations, {{GVESB}} offers a wide variety of Operations that you can use in your service. See [[plugins]] section.
 ==How To==
 From the {{L_VULCON}} Core view, it is possible to insert a new Channel by right clicking the [[System]] element you are working on. Then ''Insert after'' and press Channel*. A new Channel element will be created. Fill the ''id-channel'' property in the properties view. Now you can insert all the operations needed.

@@ Line 9: / Line 9: @@
 =={{VULCON}} / {{GVCONSOLE}} Configuration==
-The Channel is identified by an unique attribute id-channel, this attribute is unique within the System entity.The Channel subelement are the Operations, {{GVESB}} offers a wide variety of Operations that you can use in your service:
+The Channel is identified by an unique attribute id-channel, this attribute is unique within the System entity.The Channel subelement are the Operations, {{GVESB}} offers a wide variety of Operations that you can use in your service. See [[plugins]] section.
 '''File management''':

@@ Line 9: / Line 9: @@
 =={{VULCON}} / {{GVCONSOLE}} Configuration==
-The Channel is identified by an unique attribute id-channel, this attribute is unique within the System entity.The Channel subelement are the Operations, {{GVESB}} offers a wide variety of Operations:
+The Channel is identified by an unique attribute id-channel, this attribute is unique within the System entity.The Channel subelement are the Operations, {{GVESB}} offers a wide variety of Operations that you can use in your service:
 '''File management''':

@@ Line 9: / Line 9: @@
 =={{VULCON}} / {{GVCONSOLE}} Configuration==
-The Channel is identified by an unique attribute id-channel, this attribute is unique within the System entity.The Channel subelement are the Operations, {{{GVESB}}} offers a wide variety of Operations:
+The Channel is identified by an unique attribute id-channel, this attribute is unique within the System entity.The Channel subelement are the Operations, {{GVESB}} offers a wide variety of Operations:
 '''File management''':

@@ Line 4: / Line 4: @@
 Usually the '''Operations''' are grouped by:
-*Technology:Some servers may have different technological interfaces (eg HTTP, RMI), then you can allocate additional channels to group operations based on the technology used.
+*Technology: Some servers may have different technological interfaces (eg HTTP, RMI), then you can allocate additional channels to group operations based on the technology used.
-* Abstraction:It 'possible that a system is actually composed of several heterogeneous systems (such a situation can occur, for example, during a migration, or due to modification or replacement of systems). For each subsystem is possible to build a Channel.
+* Abstraction: It 'possible that a system is actually composed of several heterogeneous systems (such a situation can occur, for example, during a migration, or due to modification or replacement of systems). For each subsystem is possible to build a Channel.
 =={{VULCON}} / {{GVCONSOLE}} Configuration==

← Older revision		Revision as of 10:53, 27 February 2013
Line 1:		Line 1:
	==Description==		==Description==
		+
		+	The '''Operations''' are grouped into '''Channels''', how organize the '''Operation''' within the '''Channels''' is a choice of {{GVESB}} developer
		+
		+	Usually the '''Operations''' are grouped by:
		+	*Technology:Some servers may have different technological interfaces (eg HTTP, RMI), then you can allocate additional channels to group operations based on the technology used.
		+	* Abstraction:It 'possible that a system is actually composed of several heterogeneous systems (such a situation can occur, for example, during a migration, or due to modification or replacement of systems). For each subsystem is possible to build a Channel.
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+

	A '''Channel''' brings together a set of operations to a [[System]]. Generally, the operations contained in a channel are related to each other: for example, operations such as enqueue / dequeue that work on the same queue will be contained in the same channel.		A '''Channel''' brings together a set of operations to a [[System]]. Generally, the operations contained in a channel are related to each other: for example, operations such as enqueue / dequeue that work on the same queue will be contained in the same channel.

@@ Line 1: / Line 1: @@
 ==Description==
-A '''Channel''' brings together a set of operations to a [[System]]. Generally, the operations contained in a channel are related to each other: for example, operationss such as enqueue / dequeue that work on the same queue will be contained in the same channel.
+A '''Channel''' brings together a set of operations to a [[System]]. Generally, the operations contained in a channel are related to each other: for example, operations such as enqueue / dequeue that work on the same queue will be contained in the same channel.
 In general for any [[system]] there will be a single channel that collects all the operations necessary for communication to the system. But there may be situations where it is preferable to use multiple channels.