On 30-03-2003 20:59, "Aaron Ballman" <aaron at realsoftware dot com> wrote:
>> That was my thought too, but I write this great ;-) news-downloader that
>> does something I don't even understand myself: it communicates through port
>> 119 on the same server in various sockets, and they do not mind at all.
>
> How are you determining this (like with a tcpdump or something)? Are
> they multicasting or unicasting? Or are they doing their sends to
> 127.0.0.1 all to the same port, and they all get translated to the same
> port? Are they using multiple protocols (like TCP and UDP)?
How I determine what my own program does? Well, just looked in the source
that I wrote myself!
There are various sockets in my windows, controlled by timers that make sure
time-outs are noticed, and DataAvailable-events are handled. The sockets
have their addresses set to the same server, and to the same port (119,
standard for network news transfers). Remember, this is not about
ServerSockets, I am talking plain old 4.5.2 sockets here...
A user can choose to download a full list of newsgroups names from the
server, but at the same time he can (for I do not disable any buttons in
this alpha-version yet) run the main loop that loads pictures from
newsgroups.
Both processes run fine, without interrupting or upsetting each other. I get
the list of names complete, and at the same time see pictures coming on my
screen that are just fine. It has to be said, though, that the return codes
in the NNTP are different for loading articles and loading lists, so maybe
the two do not collide by accident... and some luck.
It surprised me, but I will still disable the one function when the other is
running in the final version.
---
A searchable archive of this list is available at:
<http://support.realsoftware.com/listarchives/search.php>
Unsubscribe:
<mailto:realbasic-nug-off at lists dot realsoftware dot com>
Subscribe to the digest:
<mailto:realbasic-nug-digest at lists dot realsoftware dot com>
.
|