Gnutella Forums

Gnutella Forums (https://www.gnutellaforums.com/)
-   General Discussion (https://www.gnutellaforums.com/general-discussion/)
-   -   Future Ports (https://www.gnutellaforums.com/general-discussion/7841-future-ports.html)

eagle3Eyes February 3rd, 2002 11:57 AM

Future Ports
 
Have I mentioned that it could happen that Network-administrators would block your Port of preference (I am sure they blocked 6346 and 7 in our University).

So what I have to do usualy is go through pages and pages of http://www.gnufrog.com listings handpicking the odd ports and hope I can make a connection. once that has happened I ad that first contact on Outgoing host to my 'Auto Connect Host' list hoping that it may (and it does often enough) work another few times.
With a first contact the next few come in themselves (only on the new 0.6.2 that seems to not work quite as well?). Continues the problem then that the Hostcatcher (I don't really knowwhere it gets its info from but it must be out of the search or answer traffic) caches all those default ports that ar blocked on my subnet... So I was asking for a Port filter for that point - and I will when I get around to analysing and understanding the structure of the Phex source see if I can do it myself...

At any rate Greatest Thanks to the Development team of douphtlessly the best Gnutela client for my purposes !

I congratulate you on your release early and often Philosophy Greg - for now I still went back to the 6.1 client cause I can manualy restart when I got a bit further but I dont have the communication why I dont get enough incoming connections sometimes - maybe its just because I feel saver to adjust (thanks for that new capability) the max search traffic to less than 5k (I got in truble before when I was running phex 0.5.x on 4 machines at the same time and maybe without knowing how much search traffic i was generating) I would like to run phex again on that many (sometimes remote) machines but for that I would like a feature 'Priority Connection' - Or even Better a Localized MULTICAST SEARCH PLASMA ? Has that ever been considered ? I don't know but I am sure it has by you progressive developer folks. I know my experiments with multicasting where not yet too succesful but it is in use Multicasting streaming audio isn't it ? So How about that if a Client participated in regular connections plus a few multicast bubbles that would reduce his local traffic because he does not have to repeat the seach packets to every one of the multicast group members.
what would be neccessary is of course some mechanism that not two clients try to act as the relay between two multicast bubbles at the same time ...

Anyhow with random ports and reasonable traffic use the admin peple can not complain and will not again dare to threten me with disconnection...

Also I thought about the multicast scheme also for sharing popular files more efficiently and possibly more than one host (of the desired morsel) can contribute packets and more than one client can enjoy the added bandwdth - of course all with propper checksumming and out of sequence reassembly ...

I hope I am not overdoing my newly reestabliched login here today!
Cheers

eagle3Eyes

eagl3Eyes February 3rd, 2002 08:49 PM

Object Oriented
 
Don't mind me if I continue thinking loud and publicly ...

Its that I still have to often manually 'intervene' and search a file and that one there is an established dObject of desire (a file that one would like to have) it should stay connected with the search that lead to it ...

I am not refering to the thing I liked about LimeWire that multiple searches can run at the same time ...

But I am also refering that I would like to stay informed of what comes back even in the automatic researches (that can then help to optimize keywords criterias or so ...) It will also become more interesting when multple hosts could be connected to download from at the same time (even though frankly I believe that will be more likely to happen when Multicast File Publishing is done

So what I am getting to is that Maybe every DesiredDownload Object should in a mode have its own screen that could be split in the search, kandidates, transfer(s) as well as patial completion map.

Shure I like to see the current Download Tab be maintained as an Overview mode - but essentialy the User may select an Option New Search/Download - refine his search there and let it result in exactly one DesiredFile (if he ever finds another File that he wants on the same search that would automatically result in a copy of the tab to another New Search/Download...

There was some more stuff I was going to explain about the previous post of mine (other than the sloppy typos) what was it again ... Shout don't remember - ask me ...

cheers

eagl3Eyes February 3rd, 2002 08:58 PM

Oh I remember 'Priority Connection'
 
<quote>
I would like to run phex again on that many (sometimes remote) machines but for that I would like a feature 'Priority Connection' - Or even Better a Localized MULTICAST SEARCH PLASMA ?
</quote>

What I mean with 'Priority Connection' is that that would be a lit of Machines that I know on my local intranet (they have a large amount of spare bandwidth). Those 'Priority Connection' would not need to count like a regular outside connection and should always (when my other Intranet Machine is up and running a Gnutela Client) be by default connected...

That explains it I would like to hear some Opinions about the 'MULTICAST SEARCH PLASMA' too - Entonces Adelante :)

free_bound February 7th, 2002 12:20 PM

couldn't you filter "ordinary" replies?
 
>So what I have to do usualy is go through pages and pages of http://www.gnufrog.com listings >handpicking the odd ports and hope I can make a connection. once that has happened I ad that >first contact on Outgoing host to my 'Auto Connect Host' list hoping that it may (and it does >often enough) work another few times.

Couldn't you tell Phex that the standard ports are invalid?
Then they wouldn't appear in the host catcher and you'd have enough odd ports.

Would something like *.*.*.*:6346 in invalid host list block all "normal" hosts?

Eagle3Eyes March 3rd, 2002 08:43 PM

Nothing yet implemented does the trick !
 
<quote>Would something like *.*.*.*:6346 in invalid host list block all "normal" hosts?</quote>

For one it does not work
For two Its not what i want to do ...
I like hosts on all ports (I can work with them (if they push))

I just don't want them in my hostcatcher
Cause I know I couldn't (without a special proxy or something) connect to tem outgoing anyway !

See my post under 6.3 release ...

GregorK March 4th, 2002 10:54 AM

We are working on a solution.

Eagle3Eyes March 9th, 2002 12:22 AM

Thanks Greg & Guys & Galls!
 
The sun will shine again
Tomorrow the rain
will blow away the muddy puddles
Of my tears for the lost
Inocense will blossom
below the Breasts
of Angels Wings waking
I will listen for your dream
coming heavens doors
pounding hearts awaiting
the warmth of forgotten nights
in naked arms raceing
what one understood
as gnutella protocoll

:)

Cheers


All times are GMT -7. The time now is 11:28 PM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.

Copyright © 2020 Gnutella Forums.
All Rights Reserved.