search

nglass / tunesremote-se

Automatically exported from code.google.com/p/tunesremote-se
5 stars 1 forks source link

JmDNS 3.4 Upgrade #10

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
TunesRemote SE is still using JmDNS 3.2 and in 3.4 he has made many bug fixes 
and improvements to the speed of the code.

Original issue reported on code.google.com by mellowaredev on 22 Aug 2011 at 11:56

GoogleCodeExporter commented 9 years ago 
I think I had issues with 3.4 on my Linux machine when I started development.
Maybe I'll give it another go

Original comment by nick.gl...@lycos.com on 23 Aug 2011 at 6:09

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Attached is a Zip you should just be able to drop into your project.

IT contains...

1. Updated JmDNS from SVN HEAD which is 50% faster than the version you are 
using now.

2. ANT script updated to be more developer friendly referencing /svnant in the 
/support folder.

3. Ant builds a Windows EXE and zips it as ..R67-WIN.zip

All been tested locally.

Original comment by mellowaredev on 25 Aug 2011 at 12:46

Attachments:

GoogleCodeExporter commented 9 years ago 
I modified the patch slightly so that the ant script selects the correct 
binaries for launch4j, change the icon and moved files around a bit.  Mind 
testing the new v74 executable that Ive built on Linux?  It seems to run in 
wine on Linux.

Original comment by nick.gl...@lycos.com on 31 Aug 2011 at 6:46

GoogleCodeExporter commented 9 years ago 
Downloaded version works great!   

The only thing is the icon looks really bad in Windows which is why I used a 
different icon that supports all the different Windows scaling options.

Original comment by mellowaredev on 31 Aug 2011 at 8:49

GoogleCodeExporter commented 9 years ago 
Latest .78 version takes a LONG time to find my library now that you have added 
the multiple interface check from jMDNS.

I almost thought it wasn't working.  maybe an indicator like "Searching for 
libraries..." or some visual cue would be great.

Original comment by mellowaredev on 21 Sep 2011 at 10:42

GoogleCodeExporter commented 9 years ago 
I think it is safe to close this ticket.  The JMDNS is slower because of the 
mutliple interfaces you now check which is worth the extra time scanning.

Original comment by mellowaredev on 11 Nov 2011 at 12:46

GoogleCodeExporter commented 9 years ago 
I think we may get a slight speed bump when I finally stop advertising pairing 
on all interfaces on startup and implement a proper "pair" button.

Thanks for the update

Original comment by nick.gl...@lycos.com on 11 Nov 2011 at 9:08