Re: Self-Updating Bundle
Re: Self-Updating Bundle
- Subject: Re: Self-Updating Bundle
- From: Tom Harrington <email@hidden>
- Date: Sat, 12 Nov 2005 14:29:30 -0700
On 11/11/05, Josh Ferguson <email@hidden> wrote:
> I'm currently trying to write a framework that is self-updating. When a
> user makes a call to the framework, it would first connect and see if
> there's an update available, and subsequently download that update and
> replace itself and then continue with the operating that was originally
> called. I'm not opposed to trying a different format (for example, using
> a static and dynamic libraries), but I'm not entirely sure how to
> approach this. This bundle/framework/library will require loading an
> objective-C class (at least indirectly, as it relies on WebKit). Has
> anyone run into this before? Even having a static stub that handles
> downloading and updating the bundle before it gets loaded would
> work...but that seems a bit unwieldy. Anyone else have any ideas on how
> to accomplish this?
I kind of suspect that your last idea might actually be the most
straightforward, since I'm guessing you don't want to have to restart
the application after an update. Since NSBundle doesn't unload, you
need to either update the code before loading it or else get into
lower-level operations. On the latter, NSModule might well do what
you need, but also might be more difficult than just checking first
and going with NSBundle.
--
Tom Harrington
email@hidden
AIM: atomicbird1
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden