new Features
 

There is nothing more annoying then being almost halfway through a 645,000 kb download and then having Limewire crash!
But the "core" of it kept right on downloading... I decided to leave it going... it failed and then I though wouldn;t it be cool if Limewire was a service on NT (2000, or XP) so that the java part controls it but the NT service part actually does the work.
I think it would be a much more stable system.
Even if the java (visible) part failed your download would continue
This also means you wouldn't have to be logged in to download/upload!
For Xp, 2000, NT users (who share there comp) this would be very helpful.
And then so that your other internet/network apps don't slow down you could have some sort of Bandwith manager - another program takes priority.
And then because it's a service you could have the comp wake up in the middle of the night download a file and then shutdown (of course u would need to know a bit about Windows and services,etc)
Then you could incorporate multiple downloads per user - so they don't open up mutiple instances of Limewire and mess everything up!
email : generalquigley@hotmail.com
*start the Subject off with LimeWire Post or I will NOT get it!

Dude...
 

Ok first this is a forum so come back here to read the answers that way everyone can read them.

The Core of Limewire is also Java! And the GUI is build on the core so if a DL breakes in the gui it has broken in the core also.

Limewire is Java (platform independent) so a NT XP or whatever feature is not really cool if Macs and Linux users can't have it.
I think you can make it run as a service on NT, XP yourself.
if you want your PC to download in the middle of the night and auto download something get a Linux! there is a client doing auto downloads.

bandwidth manager. do you want your downloads to slow down A LOT just because the other user wants to surf the internet with out slowing down? by the way: bandwidth is a limited resource and therefor it will always slow down other applications the more applications are using the internet.


mahalo

Service is just what it's called in Windows
 

Something similar is probably in every OS.
and the Gui Limewire and the Core are two seperate things that "call" on each other for resources and then one responds to the other. (at least that's what I think)
They are just designed to run together, which is probably why the download failed.

Nope, GUI and core don't have a real client-sever architecture at the moment. There are many occasions, on which the GUI directly calls methods from the core, which would be impossible, if GUI and core were running on two different JavaVMs.

Separate core and GUI
 

There are libraries such as GLUE that allow an object to be published as a service and its methods can then be called transparently using SOAP. Check out the header examples.

http://www.themindelectric.com/glue/index.html