Article View: bit.listserv.appc-l
Article #453TPIDs
From: Richard L. Gray ((919) 254-7408)
Date: Fri, 17 Dec 1993 12:59
Date: Fri, 17 Dec 1993 12:59
9 lines
1247 bytes
1247 bytes
Ummmm, Peter, you are correct for the native APPC API on OS/2. However, *CPIC* should clean up the TPID for you when the last conversation to use it ends. Otherwise you will eventually exhaust all available storage, not to mention the questions of which one to use when performing work on behalf of a client (in a cascaded server scenario, perhaps). Programmers should *not* be *forced* to use the new extensions to make their code robust. Regards, Richard.
Technical Details
Message-ID:
<APPC-L%93121708070762@AMERICAN.EDU>Path:
arc1-ca.pugleaf.net!gmd.de!newsserver.jvnc.net!howland.reston.ans.net!paladin.american.edu!auvm!VNET.IBM.COM!rlgrayShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10aed9,ee547f6b576f8059,start X-Google-Attributes: gid10aed9,public X-Google-ArrivalTime: 1993-12-17 08:51:06 PST Path: arc1-ca.pugleaf.net!gmd.de!newsserver.jvnc.net!howland.reston.ans.net!paladin.american.edu!auvm!VNET.IBM.COM!rlgray Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU Newsgroups: bit.listserv.appc-l Return-Path: <@AUVM.AMERICAN.EDU:owner-appc-l@AUVM.AMERICAN.EDU> Return-Path: <@AUVM.AMERICAN.EDU,@CUNYVM.CUNY.EDU:rlgray@VNET.IBM.COM> X-Addr: Internet: rlgray@vnet.ibm.com NO SNIVELING! Message-ID: <APPC-L%93121708070762@AMERICAN.EDU> Date: Fri, 17 Dec 1993 07:59:07 EST Sender: APPC Discussion List <APPC-L@AUVM.BITNET> From: "Richard L. Gray ((919) 254-7408)" <rlgray@VNET.IBM.COM> Subject: TPIDs Lines: 8