Advanced Questions

From PhexWiki

Jump to: navigation, search

Welcome!

If you have questions going further than "how do I download" or "how to I add something to my share", please feel welcome to post them here.

This page is being watched, so people are being informed of new questions and can answer them as fast as our real-life shedules allow. - Arne 11:24, 14 Oct 2005 (CEST)

Contents

How do I use phex behind a block-all-allow-socks-only-firewall?

- 84.160.118.199 04:10, 14 November 2005 (CET)

You can go into Options and configure your proxy-settings to use your socks-proxy. - Arne 12:11, 15 November 2005 (CET)


After upgrading to 3.0 All my music files keep getting deleted. I didn't uninstall the old version first. I have now uninstalled both versions and reinstalled 3.0. I will see how works out.

Can I use Phex with IPv6? When will I can?

--213.188.201.7 11:59, 11 February 2006 (CET)

We can't forsee this yet. It depends on our development time (we're working on Phex in our free time). If you want to help implementing IPv6 (or something different), we'd happily welcome you in the Phex Team.


Can I use Phex without gui (headless)?

Arne 23:49, 11 October 2006 (CEST)

You can use phex headless by running it from the command line via the following command:

java -Xmx512m -Djava.awt.headless=true -jar phex.jar

if you use the svn-version of phex, you can just invoke the script "buld-and-run-headless". Arne 23:50, 11 October 2006 (CEST)


What's the significance of the 1st segment being 16kbs?

There is no significance.

Other vendors should not care about how large your 1st segment is. A small size could give you an incorrectly calculate host speed, since the transfer might go very fast. This would influence the size of the 2nd segment requests. Also there is more overhead compared to the transfered data.

A larger 1st segment could block a bigger part of the file to a slow host. But generally larger segments are preferred when you host speed is not an issue and you don't care about a few slow hosts blocking the last segments. Larger segments cause less transfer overhead since more data is transfered with each request.

The follow up requests to the same host will size the segment according to the target transfer time and the calculated speed of the host. - written by gk - Arne 08:44, 22 May 2007 (CEST)


number-child
SourceForge.net Logo

Please visit our supporters
Amazon.com or Amazon.de