× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: TCP/IP Sockets -- maintaining multiple connections?
  • From: Bob Crothers <bob@xxxxxxxxxxxxxx>
  • Date: Mon, 3 May 1999 11:31:08 -0000
  • Organization: Cornerstone Communications, LLC

David,

"C" is not required, just easier (IMHO).

If you are using the scheme I have told you about, you are multi 
threaded.  Or more accurately, multi-processed.  Each "Client 
Servicing" Job is only handling one client.  It doesn't know or care 
about other connections.  If this works, then great.  If it does NOT 
work, then things will get a lot more complex (and ugly) fast.

Also, I currently target V3R1 with all of my stuff.  This probably 
wont get raised until summer of 2000.

Bob

-----Original Message-----
From:   David Gibbs [SMTP:David.Gibbs@IL.US.MKS.com]
Sent:   Monday, May 03, 1999 8:55 AM
To:     'MIDRANGE-L@midrange.com'
Subject:        RE: TCP/IP Sockets -- maintaining multiple connections?

> the accept() returns a NEW socket descriptor.  You would then
> use that
> descriptor when sending/receiving to this new box.  The sockaddr
> structure you pass is an ouput parm (output from the API).  accept() 
> puts the address information of the system requesting the 
connection.

Ah... ok, I was confused by some other sockets documentation (non '400
centric) I was reading.

> Also, this is a very good place to use threads...or something like
> them.  That way each thread only has to worry about 1
> connection.  You
> then use cross thread communications to tell the thread from server2 
> that it has data from server1 to send.  These comminations can 
happen
> via a combination of message queues  (slow), data queues
> (fast),  user
> queues (very fast) and/or mutex's.  It all depends on the specific
> application requirements.

Well, threading & C are out of the question at this point.  I have to 
target
V3R2 (lowest OS400 release we support) and I don't know C very well
(although I will admit, knowledge of C in supporting the RPGLE code 
would
certainly help).

david
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to 
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: 
david@midrange.com
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.