bright, fresh software
Downloads  |  Buy

Removing updates

Post a reply

:
In an effort to prevent automatic submissions, we require that you enter both of the words displayed into the text field underneath.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:
BBCode is OFF
Smilies are ON
Topic review
   

Expand view Topic review: Removing updates

Re: Removing updates

Post by Wyatt » November 20th, 2012, 3:37 pm

Yes, it's coming out. It has been delayed (obviously) due to bug fixes (some nasty bugs) and behind the scene process fixes.

Re: Removing updates

Post by aircan » November 20th, 2012, 3:30 pm

Is 2.7 ever coming out? I've been hoping to get incremental patches for a long time now.

Re: Removing updates

Post by gregb » April 9th, 2012, 12:03 pm

Ok thanks, I just wanted to ready to plan for it.

Re: Removing updates

Post by Wyatt » April 9th, 2012, 11:32 am

We're pushing hard for the new date: end of April. We think we can make it with the features we have planned.

Re: Removing updates

Post by gregb » April 9th, 2012, 10:44 am

Do you have a timeframe around the expectancy of a stable 2.7?

Re: Removing updates

Post by Sam » April 8th, 2012, 1:58 am

So in this current version, due to your previous comments, that means there is no way to accomplish that?


You could take hybrid approach. Include the latest patches with your server and then if one of the client computers requests an older patch, download it once and cache it, then transfer it to the client. Then subsequent requests for the old file will already be on the server computer.



So in this current version, due to your previous comments, that means there is no way to accomplish that?


No good way, not yet.

Re: Removing updates

Post by gregb » April 7th, 2012, 11:06 am

[quote="Sam"]Yes, but as I suggested, you'll have to create an admin service that accepts HTTP requests from the client machines, downloads the appropriate update file on your server, and then forwards that file to the client machine.[/quote]

Sorry maybe I left it out before but I actually wanted to store the client's updates on the server that way the server would have all the updates that client needs. I know that is possible due to the file:// location that you can pass in as a download site. My only problem with that is that I wanted to reduce the amount of updates the server had to keep hold of. So in this current version, due to your previous comments, that means there is no way to accomplish that?

So instead of the updates being hosted on a remote website or server, and the local server acting as a proxy for the client to get to those updates, I wanted to have the local server host the updates for the client. I was just trying to figure out a way to decrease the amount of updates the local server has to hold.

Re: Removing updates

Post by Sam » April 7th, 2012, 10:57 am

Yes, but as I suggested, you'll have to create an admin service that accepts HTTP requests from the client machines, downloads the appropriate update file on your server, and then forwards that file to the client machine.

Re: Removing updates

Post by gregb » April 7th, 2012, 10:42 am

So there is no way to accomplish this in the current version? No way to mimic this?

Re: Removing updates

Post by Sam » April 7th, 2012, 10:31 am

In wyBuild 2.7.x we're adding a "admin update manager" program, and pre-built Windows services that you can install on the client machines. This way you'll have a drop-in solution for both the admin and client computers.

This isn't coming with 2.7.0, though. However we're shooting for shortly after 2.7.0.

Top