[Sparkle] Avoiding an incompatible update

[Justin Bur]

SparklePlus, which I think Andy has incorporated into the trunk now,  
allows sending various system profile information as arguments on the  
http request for the appcast. The appcast is not a fixed xml file,  
but rather a php script that interprets these arguments for  
statistical purposes – or for customizing the appcast.

Although it is considered polite to ask permission before  
transmitting people's system details, I think it is legitimate to  
send just the system version number, if that is a piece of  
information you need to offer the correct update. The rest of the  
profile information should not be sent (the code to compile and  
transmit it should be commented out).

The only problem with this solution is that it won't help you unless  
you've adopted it for the release *before* the one that needs to  
decide whether you're on Tiger or Leopard... you can't really upgrade  
in the field!

Justin

On Jan 20, 2008, at 17:21, David Dunham wrote:

> I'm planning a Leopard-only update, and realized that I don't have
> anything in place to prevent a user running Tiger from updating to
> this version. How are people handling this?
>
> One thought that crossed my mind was to switch the URL that Sparkle
> uses. This would allow the Leopard only version to have Sparkle
> updates. And it would keep Tiger users safe. But it would prevent
> Leopard users from learning about the update.
>
> David Dunham           A Sharp, LLC           +1 206 783 7404
> The Opal outliner is now available!  http://a-sharp.com/opal/