On Monday 22 January 2007 12:18, Cliff Wells wrote: > The method I used was I had a basic "bootstrap" .exe file that could > parse a simple .ini file, fetch a zipfile of Python modules (since > Python can import from a zipfile now) and then finally begin fetching > the interface code in the form of XRC files. This way I only ever had > to push out .exe updates if I changed the bootstrap code (not very > often).
Wow...you just totally destroyed my productivity for the day. Now I'm going to be thinking about all these cool ways to distribute files at run time, interact with the central server, and the like. Sigh. Thanks. :) > As an aside, this was not a public application, so I didn't need to > worry a lot about security issues that pushing Python modules out > implies. As another aside, if you think that's a horrible security > issue, then I'd recommend against using easy_install ;-) I *would* > however be certain to use SSL and have the client validate the > certificate before it downloads any code. Right, I'd use SSL and probably GPG sign the zip file. Good reminders, though. > Have fun. Oh, I will. Ever been at a point where you hear a new idea, and you get giddy and silly thinking about all the new possibilities it opens up for you? Yeah, well, I'm there. Sigh. :) j -- Joshua Kugler Lead System Admin -- Senior Programmer http://www.eeinternet.com PGP Key: http://pgp.mit.edu/ ID 0xDB26D7CE PO Box 80086 -- Fairbanks, AK 99708 -- Ph: 907-456-5581 Fax: 907-456-3111 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
