HP 800 ACSE/Presentation and ROSE Interface Programmer's Guide - Page 15

What is the HP ACSE/Presentation and, ROSE Interface

Get HP 800 PDF manuals and user guides View all HP 800 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 15 highlights

APRI Overview What is the HP ACSE/Presentation and ROSE Interface What is the HP ACSE/Presentation and ROSE Interface The ACSE/Presentation and ROSE interface (APRI) provides a programmatic interface to the Association Control Service Element (ACSE), Remote Operation Service Element (ROSE) and Presentation layer protocols over an OSI network. See Figure 1-1. ACSE/Presentation Using the ACSE/Presentation (A/P) interface enables two or more application processes on the same or different computers to: • Establish an association (connection) with another application process • Exchange (send and receive) information and • Shutdown the association (connection) ROSE Using ROSE with ACSE/Presentation provides the request/reply service which is useful in building distributed applications. Note that ROSE cannot be used independently of the ACSE/Presentation interface. Support for Multi-Threaded Applications This version of HP OTS/9000 supports multi-threaded applications to be written using the same programmatic interface as before for APLI and ROSE. Applications can use either DCE User Threads or Kernel threads interfaces. The following programming guidelines need to be followed to be able to write multi-threaded applications: • The application should be compiled with the -D_REENTRANT compiler flag. Also, it may use compiler flag -D_PTHREADS_DRAFT4 for linking with DCE User Threads library or -D_KERNEL_THREADS for Kernel threads library. • Multi-threaded applications must define ap_errno as: extern unsigned long _ap_errno(); Chapter 1 15

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
Chapter 1
15
APRI Overview
What is the HP ACSE/Presentation and ROSE Interface
What is the HP ACSE/Presentation and
ROSE Interface
The ACSE/Presentation and ROSE interface (APRI) provides a
programmatic interface to the Association Control Service Element
(ACSE), Remote Operation Service Element (ROSE) and Presentation
layer protocols over an OSI network. See Figure 1-1.
ACSE/Presentation
Using the ACSE/Presentation (A/P) interface enables two or more
application processes on the same or different computers to:
•
Establish an association (connection) with another application
process
•
Exchange (send and receive) information and
•
Shutdown the association (connection)
ROSE
Using ROSE with ACSE/Presentation provides the request/reply service
which is useful in building distributed applications. Note that ROSE
cannot be used independently of the ACSE/Presentation interface.
Support for Multi-Threaded Applications
This version of HP OTS/9000 supports multi-threaded applications to be
written using the same programmatic interface as before for APLI and
ROSE.
Applications can use either DCE User Threads or Kernel threads
interfaces. The following programming guidelines need to be followed to
be able to write multi-threaded applications:
•
The application should be compiled with the
-D_REENTRANT
compiler
flag.
Also, it may use compiler flag
-D_PTHREADS_DRAFT4
for linking
with DCE User Threads library or
-D_KERNEL_THREADS
for Kernel
threads library.
•
Multi-threaded applications must define ap_errno as:
extern unsigned long _ap_errno();