Sponsored Content
Homework and Emergencies Homework & Coursework Questions C TCP/IP Reliable Transmission project not reliable Post 302833177 by kowit010 on Tuesday 16th of July 2013 11:43:34 AM
Old 07-16-2013
Never mind, I had figured it out. It involved simply moving the fprintf calls in the main while loops in both runClient() and runServer() before I wrote the "bytes_read" to "bytes_written" and sent them back and forth. No assistance needed here now!
This User Gave Thanks to kowit010 For This Post:
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Good (reliable!) check if user exists

Hi all, I've been trying to find a good check I can put it in to a shell script to see if a given user exists. Some of the things I've thought about is checking whether they have a home directory, but not all users have a home directory. I've thought about grepping the /etc/passwd file for... (4 Replies)
Discussion started by: _Spare_Ribs_
4 Replies

2. AIX

Reliable dual-boot method for 5.3 and 6.1

Hi All, I am looking for information and advice on a reliable method to support the dual booting between AIX 5.3 and AIX 6.1 I have a 7029-6E3 with 2 x 36Gb disks, hdisk0 (altinst_rootvg) and hdisk1 (rootvg) I have previously used alt_disk_install to upgrade from 5.1->5.3, and now from... (2 Replies)
Discussion started by: KevB
2 Replies

3. Shell Programming and Scripting

Most reliable way to store file contents in an array in bash

Hi Guys, I have a file which has numbers in it separated by newlines as follows: 1.113 1.456 0.556 0.021 -0.541 -0.444 I am using the following code to store these in an array in bash: FILE14=data.txt ARRAY14=(`awk '{print}' $FILE14`) (6 Replies)
Discussion started by: npatwardhan
6 Replies

4. Programming

reliable udp and socket programming

could somebody give me hand programming the attached request. my code isn't complete and i do not really understand how should i implement that. (1 Reply)
Discussion started by: makaveli_
1 Replies

5. Programming

Reliable management of signal SIGPIPE and SIGTERM

I' m note very expert in the reliable manage of signal... but in my server I must manage SIGPIPE for the socket and SIGTERM... I've wrote this but there is something wrong... Can someone explain me with some example the reliable management of signal?? This is what I've wrote in the server ... (2 Replies)
Discussion started by: italian_boy
2 Replies

6. SuSE

Is OpenSuSE 12.1 stable and reliable?

Hi, We are ready to update OpenSuSE for our web servers from 11.2 to either 11.4 or 12.1. 12.1 is still a beta version. Is it stable and reliable enough for production servers? Please share your valuable experiences. Thank you in advance! (5 Replies)
Discussion started by: aixlover
5 Replies

7. Ubuntu

Reliable Video Editing & DVD Burning

I have just about given up trying to find a reliable package. Imagination - Pitvi - Openshot - DVD Styler are just some of those tried, but even if success has been achieved in exporting a viable result - Brasero will not burn it this includes VOB files. It seems that there is no alternative to... (1 Reply)
Discussion started by: Royalist
1 Replies

8. UNIX for Dummies Questions & Answers

Is this website reliable ?

edit by bakunin: content not relevant for our site (and bordering on spam) SNIPped, thread closed. My suggestion is to - before even considering to buy anything online - put more effort in research, i.e. what the web site you write a comment at, is all about. This one here is definitely not for... (1 Reply)
Discussion started by: ethansk
1 Replies
GLUBEGINTRIM(3G)						   OpenGL Manual						  GLUBEGINTRIM(3G)

NAME
gluBeginTrim - delimit a NURBS trimming loop definition C SPECIFICATION
void gluBeginTrim(GLUnurbs* nurb); C SPECIFICATION
void gluEndTrim(GLUnurbs* nurb); PARAMETERS
nurb Specifies the NURBS object (created with gluNewNurbsRenderer()). DESCRIPTION
Use gluBeginTrim to mark the beginning of a trimming loop and gluEndTrim() to mark the end of a trimming loop. A trimming loop is a set of oriented curve segments (forming a closed curve) that define boundaries of a NURBS surface. You include these trimming loops in the definition of a NURBS surface, between calls to gluBeginSurface() and gluEndSurface(). The definition for a NURBS surface can contain many trimming loops. For example, if you wrote a definition for a NURBS surface that resembled a rectangle with a hole punched out, the definition would contain two trimming loops. One loop would define the outer edge of the rectangle; the other would define the hole punched out of the rectangle. The definitions of each of these trimming loops would be bracketed by a gluBeginTrim/gluEndTrim() pair. The definition of a single closed trimming loop can consist of multiple curve segments, each described as a piecewise linear curve (see gluPwlCurve()) or as a single NURBS curve (see gluNurbsCurve()), or as a combination of both in any order. The only library calls that can appear in a trimming loop definition (between the calls to gluBeginTrim and gluEndTrim()) are gluPwlCurve() and gluNurbsCurve(). The area of the NURBS surface that is displayed is the region in the domain to the left of the trimming curve as the curve parameter increases. Thus, the retained region of the NURBS surface is inside a counterclockwise trimming loop and outside a clockwise trimming loop. For the rectangle mentioned earlier, the trimming loop for the outer edge of the rectangle runs counterclockwise, while the trimming loop for the punched-out hole runs clockwise. If you use more than one curve to define a single trimming loop, the curve segments must form a closed loop (that is, the endpoint of each curve must be the starting point of the next curve, and the endpoint of the final curve must be the starting point of the first curve). If the endpoints of the curve are sufficiently close together but not exactly coincident, they will be coerced to match. If the endpoints are not sufficiently close, an error results (see gluNurbsCallback()). If a trimming loop definition contains multiple curves, the direction of the curves must be consistent (that is, the inside must be to the left of all of the curves). Nested trimming loops are legal as long as the curve orientations alternate correctly. If trimming curves are self-intersecting, or intersect one another, an error results. If no trimming information is given for a NURBS surface, the entire surface is drawn. EXAMPLE
This code fragment defines a trimming loop that consists of one piecewise linear curve, and two NURBS curves: gluBeginTrim(nobj); gluPwlCurve(..., GLU_MAP1_TRIM_2); gluNurbsCurve(..., GLU_MAP1_TRIM_2); gluNurbsCurve(..., GLU_MAP1_TRIM_3); gluEndTrim(nobj); SEE ALSO
gluBeginSurface(), gluNewNurbsRenderer(), gluNurbsCallback(), gluNurbsCurve(), gluPwlCurve() COPYRIGHT
Copyright (C) 1991-2006 Silicon Graphics, Inc. This document is licensed under the SGI Free Software B License. For details, see http://oss.sgi.com/projects/FreeB/. AUTHORS
opengl.org opengl.org 06/10/2014 GLUBEGINTRIM(3G)
All times are GMT -4. The time now is 02:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy