plans to use BITS in OCS

[andreas.moroder-wON1u+O0wKj/]

Hi Andreas,
There is currently no plans to use BITS in the Windows agent. I see
this feature is .NET dependent and we do not use the .Net framework
with for the Windows agent. We use standard C++ for the Windows
agents.
What are the advantages of BITS for package download instead of
using HTTP as we already do ?
Kind regards,
--
Guillaume

Hello Guillaume,

sorry that I sent the first post directly to you mail address and not
to the mailinglist too.

AFAIK the advantage of BITS ( that uses http as protocoll ) is that
it intelligently downloads packets only when there is idle badwith.
Using bits would free the OCS client from all the part of code that
tries to do the same by downloading packages piece per piece (
CYCLE_LATENCY, FRAG_LATENCY ... )

Bye
Andreas

[andreas.moroder-wON1u+O0wKj/]

Hi Andreas,
There is currently no plans to use BITS in the Windows agent. I see
this feature is .NET dependent and we do not use the .Net framework

Hello,

the orginal BITS API does not depend on .net (**)

Take a look at http://msdn.microsoft.com/en-us/library/aa363160.aspx

Bye
Andreas

** here the foundation for my assertion:
http://msdn.microsoft.com/en-us/library/ms997639.aspx

[E Guillory]

Hi,

Bits is a good idea but only for windows (no source code) and there is currently no linux complient version.
Thus for a 100% functional usage you have to use a iis server. This is not the goal of OCS.
OCS has basically all we need to optimize and secure transfert, charge and data using https/http, fragments size, frag_latency and period_latency parameters.

Today theses parameters are manually set by the GUI.
Perhaps colud we think about a dynamic scale for them on the agent side.

A very simple way to do this could be a new value like (DYN) for frag_latency.
At this point if agent has "DYN" then frag latency will be calculated for each fragment with:
frag_latency = K*T
where T= the time needed to download the previous fragment
and K a scaling value for the banwith usage.
Of course a max value for "T" must be defined
I'm sure this can be very efficent especially with small fragments.

Wee need to change few code on server an agents and do tests.

could this help you? let us know.

Regards

Emmanuel

|
| ----- Mail transféré -----
| De: "andreas moroder" <andreas.moroder-wON1u+O0wKj/***@public.gmane.org>
| À: "developers en" <developers.en-XRi04JE7P7s3GMRc9dnpK0B+***@public.gmane.org>
| Envoyé: Mardi 25 Mai 2010 22:01:34
| Objet: Re: plans to use BITS in OCS
|
| >> Hi Andreas,
| >>
| >> There is currently no plans to use BITS in the Windows agent. I see
| >> this feature is .NET dependent and we do not use the .Net framework
|
| Hello,
|
| the orginal BITS API does not depend on .net (**)
|
| Take a look at http://msdn.microsoft.com/en-us/library/aa363160.aspx
|
| Bye
| Andreas
|
| ** here the foundation for my assertion:
| http://msdn.microsoft.com/en-us/library/ms997639.aspx
|