jemplode autoupdate

Hi.

I think I posted this before, but anyway:
jEmplode only checks for a newer version of itself only _after_ selecting an empeg. I understand that HiJack can't be tested for without an empeg being selected, but why (the heck) do I have to select an empeg before it checks for jEmplode updates?

Is this by pure chance, or did you decide to do this for a reason? If the latter is the case, then what reason was it?

cu,
sven

Yeah .. that one's in my list of things to do ... it was just kind of annoying to fix

I'd like to ask if we could specify the way Hijack and Jemplode are updated.

I dont think it exists at now.

At home I use my DSL connexion toi update but At work I have to go trough a proxy and when I launch Hijack Update from Jemplode that does not run ...

Ah, proxy support.

Coding in proxy support (especially if it's an authenticated proxy that requires username and password) is a big can of worms for most applications. Dunno if it's easy to do in Java or not. If Mike can pull it off, it would be interesting to see it work.

It's a huge pain in the butt actually ... Annoyingly I have all the code to do every proxy configuration under the sun, but it's all code that I wrote for a project at work, so it's pretty much offlimits. There is a java HTTP library that is really nice, though, that probably could be used (at least for the updates stuff). I think there is better SOCKS support in the newer VM's though, so it may be possible to even proxy the Empeg connection through SOCKS ...

Basically, I wouldn't look for this for a couple versions ... it's not a very high priority as I've only really heard two people even bring it up... But I can certainly be swayed.

Mike

Support looking for a new version in a set place on disk and an external program to get it there (wget, curl, whatever). My cow orker leads me to believe that the equivalent of system() in Java is easy, and it means you get to be lazy. Well, except on Windows I guess.


Eh. Never mind

System.exec(..) is kind of equivalent to the devil in Java... But I'll continue to look into this one.