Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!MGMT4.NCSL.NIST.GOV!brady
From: brady@MGMT4.NCSL.NIST.GOV (Kevin Brady)
Newsgroups: comp.protocols.iso.dev-environ
Subject: Re: PEPY
Message-ID: <9002141412.AA15822@mgmt4.ncsl.nist.gov>
Date: 14 Feb 90 14:12:34 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: National Institute of Standards and Technology
	formerly National Bureau of Standards
Lines: 51










      >     I am involved in a project that will  build  a  network
      >management  system  using the encoder/decoder of ISODE.  The
      >use of the CMIP/CMIS protocol is  required,  using  PEPY  to
      >create the structures and  encode/decode routines.





      >     The problem: PEPY creates structures with  pointers  to
      >other  structures  containing pointers and so on. We need to
      >pass a "message" between processes composed of these  struc-
      >tures.   To  accomplish  this over a socket leaves a "piece-
      >meal" approach as the only alternative for a bcopy. This  is
      >totally unacceptable, does anyone know of a way to have PEPY
      >generate "instances" rather than pointers??



      Let me try to be a little more specific:

  
      We will run the ASN.1 code for CMIP/CMIS thru PEPY to create 

      the encoder/decoder code and data structures to be used. These data 

      structures must then be filled in before handing them to the encoder/decoder

      for processing. The problem is that a "USER" process fills in these

      data structures and must pass this message to the process that contains

      the encoder/decoder (SMAE). The "passing" I am talking about is between

      two processes, not the encoded PDU that goes out on the network. 






                                                      Kevin Brady