Main Page   Compound List   File List   Compound Members   File Members  

ce_jops_t Struct Reference

#include <ce.h>

List of all members.

Public Attributes

ce_time_t hrtbt_rate
char transports [CE_TRANSPORT_MAX_SIZE]
char protocol [CE_PROTOCOL_MAX_SIZE]
char group_name [CE_GROUP_NAME_MAX_SIZE]
char properties [CE_PROPERTIES_MAX_SIZE]
ce_bool_t use_properties
ce_bool_t groupd
char params [CE_PARAMS_MAX_SIZE]
ce_bool_t client
ce_bool_t debug
ce_endpt_t endpt
char princ [CE_PRINCIPAL_MAX_SIZE]
char key [CE_KEY_SIZE]
ce_bool_t secure


Detailed Description

A request structure that describes the list of properties an application wishes from a created endpoint.

The format for the string arguments is that they are either all zeros, or, look like a C-string: set of non-zero characters at the beginning, followed by zeros. There has to be at a terminating NULL character.


Member Data Documentation

ce_bool_t ce_jops_t::client
 

Are we a Client?

ce_bool_t ce_jops_t::debug
 

Use the debugging version

ce_endpt_t ce_jops_t::endpt
 

the requested endpoint name

char ce_jops_t::group_name
 

The group name

ce_bool_t ce_jops_t::groupd
 

Use the group daemon?

ce_time_t ce_jops_t::hrtbt_rate
 

The heartbeat rate

char ce_jops_t::key
 

The security key, has to be either all zerosL, or of CE_KEY_SIZE

char ce_jops_t::params
 

The set of parameters

char ce_jops_t::princ
 

My principal name (security)

char ce_jops_t::properties
 

The set of properties

char ce_jops_t::protocol
 

The protocol stack to use

ce_bool_t ce_jops_t::secure
 

Do we want a secure stack (encryption + authentication?

char ce_jops_t::transports
 

The transport protocols [UDP,TCP,MCAST]

ce_bool_t ce_jops_t::use_properties
 

Use the properties, instead of the protocol ?


The documentation for this struct was generated from the following file:
Generated at Wed Dec 18 18:38:45 2002 for CE by doxygen1.2.6 written by Dimitri van Heesch, © 1997-2001