MacPhex 0.8 preview working good
 

The preview-version of phex for MacOSX works good for me.

It finds files and gets connected, and it downloads well enough.

Only drawback is, that it still has bugs (what else did you expect? :-) ) and, that it needs hours to get the list of my shared files (my computer is slow so that might not be the programs fault).

I can use Gnutella again!

Thank you, Gregor!
Thanks to the whole MacPhex-Team to enable me to use this software!
Will it support magnet-links, when 0.8 is done?

Hi..

please post or email all bugs you find, that helps me to fix them. A preview for PC and other system will be available soon too.

Phex 0.8 will support:
Partial File Sharing
Upload and Download Queuing
GWebCache
Ultrapeer Connections
and many other new features and improvements...

Gregor

first freezing bug
 

When I doubleclick a search-result, phex freezes.
When I click download or quick download, everything works.

"View the Bitzi Ticket" (whatever that means) only displays an error message (Failed to launch Browser: "FailedToLaunchBrowserURLInClipboard") and offers two buttons (no and yes), which both close the error-message.

Listing my shared-files takes about a minute a file (for ebooks) and the filelist 8with hsh1) isn't saved, so phex repeats to list slowly at every new startup.

Maybe you could create a low-tech versin of phex one day, which would only include the simplest functions, but made participating possible even for complete DAUs.

Phex vere estas bonan programon!
Arne Bab.

Can you send me your phex.log file to phexmail@gmx.net
You should find it in the .phex subdirectory of your home directory.

The message text for the browser launch error is still missing if you press 'Yes' the URL is in your clipboard and you can past it into your browser manually.

I will think about offering a low-tech version. But currently its work enough to support all the current Gnutella features.

Thanks for the feedback,
Gregor

Log Sent.

Why does phex have a hostlist of about 1,250 hosts after less than an hour?
Can it ever check all those hosts?

Also I'd like to have a "clear-hostlist" button, when it grew too big again :-)

Is there a way, that phex can check the hosts' value, before adding them to the hostlist?

You can influence the number of host IP to collect with the property 'mNetMaxHostToCatch' in your phex.cfg file.
Don't wonder there is a little bug that causes less host to be loaded when restarting Phex. I will fix this soon.
The host list is used to let Phex find an entry point to the network. Since most of these IP's have a very short live time many of them are collected. The IP's are collected from the GWebCache and from currently connected Peers.
The IP's are sorted by priority. There are three priority levels: Ultrapeer, Normal Peers and Private IPs. Inside each priority level new IP's are put on top pushing old IP's down.
When connecting the top most IP is taken from the three concatenated priority lists.

Why would you like to be able to clear the list?

Phex only checks if the new IPs are valid before adding them to the list. A connection to check the host would be too expensive.

Gregor

I want to be able to clear the list, because it can be faster, to take only those IPs from autoconnect hosts, instead of my own, when I wasn't online for a long time (or didn't run phex for a long time).

Maybe you could include that in prefs, that noone clicks at it accidently, or make a warning appear, which asks, if I really want to do that.

Bab.

Actually I like to drop the support of the auto connect list. Almost all auto connect hosts dont work anymore and the gnutella bootstrap is now done using GWebCache.
To connect to any host you can use the 'Connect to' field that remembers the entered IP, you can connect to them any time again.
When you click on Query GWebCache new IPs are fetched from the GWebCache and are put on top of your host catcher list, this allows fast connection to new hosts.

Gregor

But then, phex couldn't be used anymore to form private networks of maybe 100 persons, from which some have static ips and serve as autoconnect hosts.

Maybe you could let Users decide what to use, GWebCahce or autoconnect, or both.

But maybe you could take autoconnect hosts off the general interface and into prefs. That would ease up the connection-window.