t_rcvconnect.c revision 2
2N/A * The contents of this file are subject to the terms of the 2N/A * Common Development and Distribution License, Version 1.0 only 2N/A * (the "License"). You may not use this file except in compliance 2N/A * See the License for the specific language governing permissions 2N/A * and limitations under the License. 2N/A * When distributing Covered Code, include this CDDL HEADER in each 2N/A * If applicable, add the following below this CDDL HEADER, with the 2N/A * fields enclosed by brackets "[]" replaced with your own identifying 2N/A * information: Portions Copyright [yyyy] [name of copyright owner] 2N/A/* Copyright (c) 1984, 1986, 1987, 1988, 1989 AT&T */ 2N/A/* All Rights Reserved */ 2N/A * Copyright 2005 Sun Microsystems, Inc. All rights reserved. 2N/A * Use is subject to license terms. 2N/A#
pragma ident "%Z%%M% %I% %E% SMI" /* SVr4.0 1.3 */ 2N/A * t_rcvconnect() is documented to be only called with non-blocking 2N/A * endpoints for asynchronous connection establishment. However, the 2N/A * direction taken by XTI is to allow it to be called if t_connect() 2N/A * sent down). This implies that an interrupted synchronous connection 2N/A * establishment which was interrupted after connection request was transmitted 2N/A * can now be completed by calling t_rcvconnect() 2N/A * User level state verification only done for XTI 2N/A * because doing for TLI may break existing applications 2N/A "t_rcvconnect: Invalid state on event T_RCVCONNECT");
2N/A * Update attributes which may have been negotiated during 2N/A * connection establishment for protocols where we suspect 2N/A * such negotiation is likely (e.g. OSI). We do not do it for 2N/A * all endpoints for performance reasons. Also, this code is 2N/A * deliberately done after user level state changes so even 2N/A * the (unlikely) failure case reflects a connected endpoint.