You folks are misunderstanding:
libnfs 1.6.2 fixes your artwork issues (you only got these when libnfs was dropped back to 1.3)
'my fix', now in Gotham nightlies, appears to effectively fix the library dumping issue
Thus Gotham *should* be ok, as it comes with both of these things
The better fix, though - that solves the real underlying cause of the issue, this socket linger thing - is not going to be in Gotham - I presume because Memphiz considers it untested and there is too short a timescale to get it in and properly test it before Gotham is released. (Happy to help there if you change your mind on the @
Memphiz but I can see your point!)
I personally will be using a libnfs with this fix (it's just a drop in replacement). Especially if you're stressing the whole nfs connections thing (i.e. lots of rapid back and forth and open/closes, so library updates/cleans especially I guess) - even with 'my fix' there is the possible potential for all the lingering sockets to create issues. It's more theoretical than anything else (I think - my Gotham testing is still relatively limited as this fix has been around only a week or so!), but the purist in me wants the proper fix in place.
To that end, I'll be saving that libnfs.dll here kinda permanently:
https://dl.dropboxusercontent.com/u/1088...libnfs.dll - if anyone has any practical issues they can just drop that in and maybe a Gotham point release will have it in place anyway etc.
@
patseguin - the reason many of us are so keen on NFS in general is performance. I've done quite a bit of testing with it, and it's definitely significantly quicker than SMB on the three networks I've measured it on. (you'll see the odd perosn say SMB is just as quick but they've never actually measured it in practise in my experience they just say it seems as quick - but if you measure throughput of either single large files, OR of long lists of small ones, I have seen NFS being 30 to 50% quicker).
I used it initially because it was the only thing that made streaming 720p/1080p over ethernet-over-power devices possible back a few years ago with camelot (using autofs to mount nfs shares at the system level before the in built nfs came along) - SMB just couldn't do this. I new NFS was better for this from even back in the Popcorn Hour/HDX streaming days...old trick (and where I first encountered Hanewin NFS - that was $20 well spent, here I am almost 10 years later still going strong with it!).
I've since wired in ethernet anyway, and wireless N (or AC) is actually quite capable of this too now, but once I'd moved over I also noticed less weird sporadic issues than with SMB (no master browser hassles (Openelec elects itself master browser by default and this causes issues with some - also there was an SMB random hanging issue there's a long thread about back in 2009) - but also it's more easy to manage shares (just one config file vs. having to go into properties separately for each drive). In practice these days the most noticeable performance benefit for me is when looking at long folders of pictures from a shared drive (I have all my family photos from 2007 on running through xbmc for example)....these lists are way quicker with NFS than SMB.
