Hm. It is still not clear from your description that the heartbeats and data transfers take place concurrently.
- Does a test result data transfer take longer than 10 seconds?
- Do you actually see a heartbeat get sent from client to server, whilst the a data transfer is in progress from server to client?
(I'm not sure that this is even possible!)
- If so, what happens about the servers reply to the heartbeat?
Does it suspend the data transfer in order to send the reply?
Or does the reply get delayed until after the transfer completes?
Or does the server ignore heartbeats sent whilst a data transfer is in progress?
I suspect that the logic is more likely, the client sends a heartbeat every 10 seconds unless a data transfer is currently in progress.
If that is the case, the requirements are actually quite simple. But as you've described so far, I don't think they are possible, using threads processes or a select loop.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
