sorry Joe if i wasn't clear,  what i was trying to say is I know there is a 
solution to address the bandwidth issue caused by updates for OS X machines,   
I am unsure if they have a similar solution for their hand held devices.    I 
am assuming they do or soon will.   I'm on the road right now,  when I return 
to the office I'll take a look at the OS X update server and see if there is 
any provisions for the iPhones and friends.  

perhaps a squid caching server in-between the device network and internet?    
back in the day this is how i mitigated other many to one client update issues.

-g




On Aug 18, 2010, at 3:07 PM, JoeSox wrote:

> Interesting.
> Do you have to configure the iPhone devices or just use its standard settings?
> 
> --
> Thanks, Joe
> 
> 
> On Wed, Aug 18, 2010 at 12:03 PM, Greg Whynott <[email protected]> 
> wrote:
>> I set up an OS X server which hosts updates for the rest of the company,  so 
>> the OS X client machines poll/pull updates from the internal machine as 
>> opposed to 100 of them pulling the same updates over the internet.  saves 
>> bucket loads of bandwidth and  you can "pre ok" individual packages,  so the 
>> client just updates without prompting.   I'm not sure but I suspect they 
>> might have something which allows their other devices to poll this same 
>> source.  it would seem reasonable anyway..
>> 
>> probably not a very useful answer but there it is.  8)
>> 
>> 
>> -g
>> 
>> 
>> On Aug 18, 2010, at 2:54 PM, JoeSox wrote:
>> 
>>> Am I the only one that gets ticked off at the Apple iPhone update
>>> procedure and the amount of bandwidth it needs?
>>> Is there any secret I am missing to cut down on the required bandwidth
>>> needed for it (caching the update somewhere etc)?  I don't own an
>>> iPhone (DroidX user here) and am unfamiliar with the update, all I
>>> know is it uses tons of BW.
>>> 
>>> 
>>> --
>>> Thanks, Joe
>>> 
>> 
>> 
> 


Reply via email to