This is a more dynamic version of the element-per-transaction method. Here, you use a new element for each request. As you complete each request, the element returns to the pool. As a modification to this method, you can use one NIB and one RPL for all session-establishment and termination requests, and obtain additional pool elements for subsequent data-transfer requests. You can assemble the NIB and RPL for session establishment and termination in the application program; they do not need to come from a pool.

To maintain a strict "element per request" technique, the data area portion of an element can be used to hold an NIB for session-establishment and termination requests, and as a data area for data transfer. To do this, one NIB can be set up in the application program. For each request, the contents of the NIB can be moved into the data area in the pool element, or a GENCB can be used to build a complete NIB in the data area. This reduces the size of the pool elements.