ITK Function Reference
(V10000.1.0.60_20160308.00)
Main Page
Related Pages
Modules
Data Structures
Files
File List
Globals
publication
dist_errors.h
Go to the documentation of this file.
1
/*==================================================================================================
2
3
Copyright (c) 2004 Electronic Data Systems Corporation
4
Unpublished - All rights reserved
5
6
====================================================================================================
7
File description:
8
9
Errors for the Application Distribution ITK
10
11
====================================================================================================
12
Date Name Description of Change
13
25-Feb-2004 Tom McCabe remote checkin-checkout project
14
26-Feb-2004 Tom McCabe add DIST_object_is_local error
15
19-Feb-2006 Tom McCabe on demand sync
16
10-Apr-2006 x_aravin Added support for tracking the owning site (after merge from Tom Mccabe)
17
$HISTORY$
18
==================================================================================================*/
19
20
#ifndef DIST_ERRORS_H
21
#define DIST_ERRORS_H
22
23
/* When/if the "DIST_" ITK is released to the customer, we'll need to include without module */
24
#include <
common/emh_const.h
>
25
26
#define DIST_unsupported_client (EMH_DIST_error_base + 1)
27
#define DIST_no_server_handler (EMH_DIST_error_base + 2)
28
#define DIST_unsupported_operation (EMH_DIST_error_base + 3)
29
#define DIST_server_handler_registered (EMH_DIST_error_base + 4)
30
#define DIST_invalid_server_type (EMH_DIST_error_base + 5)
31
#define DIST_argument_error (EMH_DIST_error_base + 6)
32
#define DIST_object_is_local (EMH_DIST_error_base + 7)
33
34
// DIST_no_replica_objects, DIST_all_objects_failed, DIST_tracking_owning_site are at 8,9,10
35
// respectively(in 9.1.3 MP2 onwards). If you happen to add these error code here add with
36
// respective error code.
37
// Other wise backword compatibility with 9.1.3 would be broken.
38
// This is the reason I am changing the error code of following as per PR#5521720
39
#define DIST_no_replica_objects (EMH_DIST_error_base + 8)
40
#define DIST_all_objects_failed (EMH_DIST_error_base + 9)
41
#define DIST_tracking_owning_site (EMH_DIST_error_base + 10)
42
#define DIST_object_is_not_local (EMH_DIST_error_base + 11)
43
#define DIST_cannot_checkout_replica_from_hub (EMH_DIST_error_base + 12)
44
#define DIST_MS_TIE_invalid_parameter_creation (EMH_DIST_error_base + 13)
45
46
/*
47
* DIST_no_server_handler -> No handler is registered for the given application and server type.
48
* DIST_unsupported_operation -> A handle is registered for app_name for the given server, but the handler rejects client
49
*
50
* Either of these should be further qualified by pushing on top of them, a DIST_unsupported_client. For example:
51
*
52
* For example, for DIST_no_server_handler:
53
*
54
* "The client version 8.1.0.3 is unsupported by the server version 10.0.0.0"
55
* "No ODS server handler registered for application xxxx"
56
*
57
* or for example, for DIST_unsupported_operation:
58
*
59
* "The client version 8.1.0.3 is unsupported by the server version 10.0.0.0"
60
* "Operation 2 of application xxxx is unsupported"
61
*
62
* This still doesn't do much for a "newer" client relative to an "older" server scenario.
63
* As the distributed application evolves, you might want to code a "newer" client
64
* to do things the "old" way when dealing with an "old" server and the "new" way when
65
* dealing with a server that understands the new way. This should be handled by the
66
* client using DIST_version_check to interrogate server for its version.
67
*/
68
#endif