In the past ten months or so, a number of independent non-affiliated "Napster" servers have been developed. (See opennap.sourceforge.net for a popular example of such a server.) A Windows application, Napigator, and an accompanying web page, www.napigator.com, index these independent servers. Basically, Napsack retrieves a server index from www.napigator.com and queries each service on the list, printing the results to stdout.
I wrote Napsack because going to www.napigator.com and querying each server manually was a pain, especially for rare material; Napsack removes the connect-query-disconnect-repeat drudgery out of my (and hopefully your) Napster experience. Now you can connect to a server after verifying that it contains something interesting.
For more info, the Docs section has a couple of high/user-level discussions of Napsack.
For a more detailed account of what goes on, the source-code (in the Napsack-X.XXx/src directory of any release) would be your best reference. For a bottom-up perspective, look at the napsack.servers, napsack.protocol, napsack.commands, and napsack packages, in that order. Reverse the order for a top-down introduction.
Thank you for your offer, but I'm not looking for help right now (except for testing, please submit any bugs you find!). The code is Free software, though, so you are permitted to modify/improve it according to the GPL.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been out of the napster scene for the
past ten months since I was moved to solaris.
(ergh).
I'm intrested in napsack, could you tell me more.
(what it does etc.)
I might me intrested in helping to improve it.
I'm a java developer.
Jeff.
Hi Jeff:
In the past ten months or so, a number of independent non-affiliated "Napster" servers have been developed. (See opennap.sourceforge.net for a popular example of such a server.) A Windows application, Napigator, and an accompanying web page, www.napigator.com, index these independent servers. Basically, Napsack retrieves a server index from www.napigator.com and queries each service on the list, printing the results to stdout.
I wrote Napsack because going to www.napigator.com and querying each server manually was a pain, especially for rare material; Napsack removes the connect-query-disconnect-repeat drudgery out of my (and hopefully your) Napster experience. Now you can connect to a server after verifying that it contains something interesting.
For more info, the Docs section has a couple of high/user-level discussions of Napsack.
For a more detailed account of what goes on, the source-code (in the Napsack-X.XXx/src directory of any release) would be your best reference. For a bottom-up perspective, look at the napsack.servers, napsack.protocol, napsack.commands, and napsack packages, in that order. Reverse the order for a top-down introduction.
Thank you for your offer, but I'm not looking for help right now (except for testing, please submit any bugs you find!). The code is Free software, though, so you are permitted to modify/improve it according to the GPL.