We've just posted the LimeWire 3.5.1 beta on both the free download page and the pro download page. The pro download is available from your pro download page, and the free download is available at:

http://www.limewire.com/english/content/beta.shtml

3.5.1 adds many new features to improve your searching and downloading experience. These changes include:
- iTunes integration on OSX. When an audio download finishes, it will automatically be added to a 'LimeWire' playlist in iTunes.
- Easier bug reporting. You can now help us debug by simply clicking 'Send' when an internal error occurs. You still have the option to review the information before it is sent.
- Better validation on extra download sources, ultimately saving bandwidth and improving download success rates.
- Stalled downloads will now correctly die, allowing other sources to finish the download.
- More sources in search results.
- More aggressive download behaviour. LimeWire will now always attempt to find an active downloader, even if you're waiting in line from some hosts.
- More options for search results, downloads, uploads, connections and the library. By right-clicking (or control-click on macs) on the column headers of tables, you can choose to whether or not you want to display tooltips or row stripes, or if you want that table to be sorted automatically (automatic sorting is currently not available in search results).

Numerous bugs are also fixed.

As always, thanks very much for everyone's help testing the betas!

-The LimeWire Team

Thanks--appreciate you taking the time for the changelog.

Looks good with 3.5.1jum205 so far (sample bug message doesn't copy on the G4 Mac, but does on the G3).

[edit: LWPro3.5.1 Beta copies the sample message on the G4]

Ditto! Thanks Adam.

Hé!
Everything seems to be working on the bright side for now. I have a question to Sam or Adam, is the NIO java technology included in the 3.5 series? I've not found a decrease in memory consumption yet (maybe it is planned for, say 3.6).

Merci de votre temps,

>is the NIO java technology included in the 3.5 series?

Nope. Converting to using the NIO classes is a huge undertaking.

>I've not found a decrease in memory consumption yet

3.5 doesn't have any large changes in memory consumption. Of course, we constantly are reviewing to speed up the slowest points in the code as well as trim down the largest memory abusers. Somewhat unfortunately, all the 'easy' ones have already been taken care of... so further changes will require some heavy sleuthing and changing.

FYI, there are also a few other notable changes with 3.5.1:
- Windows users (using the English version) now have the option to start LimeWire on system startup. This will significantly help the network, as well as improve the speed with which LimeWire starts when you want to use it -- it will pop up immediately and be ready for searching.
- Upload queueing logic is improved. LimeWire will now allow an upload if it notices that enough upload slots are available for a particular queued upload AND all of the uploads that are before it. This will reduce the amount of time that downloaders will have to 'wait in line' for a file, as well as increase the speed with which files can spread throughout the network.

Thanks Sam, version 3.5 hasn't crashed overnight for me, it seems stable (usually since 3.3 I can run it for days which is rock stable for me). FYI i'm running the os x basic version and not the JUM java 1.4 version which GUI freeze every hour or two.

The Resume/Find Sources Button is really good (how can it find more sources than using repeat search from the search tab?). Wish we'd hear more about its success, eh!

Lots of interesting stats, like the crawler hits. Would 13 be normal in 6 hrs, and is this how LW gets netsize?

The UP, searches, downloads and uploads working very smoothly on the G4 Mac (non-jum; slow 128 Kbps connection through the NAT)--two power failures last night but all resumed smoothly.

In comparison, the G3 is using a direct 1mbps connection, and nada. Can't find a proxy (jum205), so no search results, downloads, uploads and the Sandvine won't be removed till next week. Such p2p controls sure waste bandwith.

That's a good question, did LimeWire already implement the "Crawler: " header for its crawler? The old crawler should not be counted by this statistics but I think requests from BearShare's crawler and the BayTSP crawler should be counted.

Yeah, I tried to contact Sandvine, telling them about the GDF & asking them if there is anything the clients could do to optimize the behaviour of their product but I didn't get any answer yet and I don't really expect one.

(aside) the improvements in LW since those dreary days in January are remarkable. I can trust today's LW enough to use it to compare ISP's. When LW doesn't work, it's getting more probable that the problem is upstream. Maybe your contact will be answered and reinforce the idea gnutella is an open community. Let the proprietary protocols take the heat.

[and thanks for working on that proxy patch: just another confirmation of LW's decision to go multiplatform and opensource]

Anyway, back to waiting for more info and insights.

Yup - big improvement to 3.5.1

I'm not quite sure if it was an intended consequence of this latest upgrade, but where previously attempting to share more than 7-8 thousand files on my PC caused problems, 3.5.1 seems stable with at least 13.

Muchos gracias/