Persistence framework design discussion - Revision history

Bertrand Meyer at 00:33, 27 August 2007

2007-08-27T00:33:23Z

Marco Piccioni: /* Consistency of the names */

2007-08-19T10:08:12Z

‎Consistency of the names

Marco Piccioni: /* Consistency of the abstractions */

2007-08-19T10:08:02Z

‎Consistency of the abstractions

Marco Piccioni at 10:07, 19 August 2007

2007-08-19T10:07:42Z

New page

==Consistency of the abstractions==
As there is a specific manager for binary serialization, perhaps it makes sense to move the features store, retrieve, store_handler and serializer from BINARY_FORMAT to BINARY_SERIALIZATION_MANAGER. One reason could be cohesion within BINARY_SERIALIZATION_MANAGER. Another reason could be that it is not clear how much the before mentioned features match with the BINARY_FORMAT abstraction.
==Consistency of the names==
The names store and retrieve, that are already used in the EiffelBase serialization cluster can be questioned. Another proposal could be to use put and item, for consistency with the structures cluster.

← Older revision		Revision as of 00:33, 27 August 2007
Line 1:		Line 1:
		+	[[Category:Persistence]]
	==Consistency of the abstractions==		==Consistency of the abstractions==
	As there is a specific manager for binary serialization, perhaps it makes sense to move the features store, retrieve, store_handler and serializer from BINARY_FORMAT to BINARY_SERIALIZATION_MANAGER.		As there is a specific manager for binary serialization, perhaps it makes sense to move the features store, retrieve, store_handler and serializer from BINARY_FORMAT to BINARY_SERIALIZATION_MANAGER.

← Older revision		Revision as of 10:08, 19 August 2007
Line 7:		Line 7:

	==Consistency of the names==		==Consistency of the names==
−	The names store and retrieve, that are already used in the EiffelBase serialization cluster can be questioned. Another proposal could be to use put and item, for consistency with the structures cluster.	+	The names store and retrieve, that are already used in the EiffelBase serialization cluster can be questioned.
		+
		+	Another proposal could be to use put and item, for consistency with the structures cluster.

@@ Line 1: / Line 1: @@
 ==Consistency of the abstractions==
-As there is a specific manager for binary serialization, perhaps it makes sense to move the features store, retrieve, store_handler and serializer from BINARY_FORMAT to BINARY_SERIALIZATION_MANAGER. One reason could be cohesion within BINARY_SERIALIZATION_MANAGER. Another reason could be that it is not clear how much the before mentioned features match with the BINARY_FORMAT abstraction.
+As there is a specific manager for binary serialization, perhaps it makes sense to move the features store, retrieve, store_handler and serializer from BINARY_FORMAT to BINARY_SERIALIZATION_MANAGER.
 ==Consistency of the names==
 The names store and retrieve, that are already used in the EiffelBase serialization cluster can be questioned. Another proposal could be to use put and item, for consistency with the structures cluster.