Subhash Chopra wrote:
> Hi Fabian,
>
> Can you give me some pointers from where i can get the source code for the 0.9
> build.. I am behind firewall so cant access the code via CVS.
In this case you will have to wait a couple of days for 0.9 to be
released. It won't be long until 0.9 is released to the public. If you
really can't wait, the 0.8.1 source code is in
http://ftp.mozilla.org/pub/mozilla/releases/mozilla0.8.1/
The 0.9 source code will be in
http://ftp.mozilla.org/pub/mozilla/releases/mozilla0.9/
Those will of course be tarballs.
Hope this helps,
Fabian.
>
> Regards,
> -subhash
>
> Fabian Guisset <[EMAIL PROTECTED]> wrote:
> Hi Subhash,
>
> Very glad you are interested in helping the project, welcome!
> You might wanna send those posts to netscape.public.mozilla.netlib, this
> is where all the networking discussion is going on. Also just for your
> information, M18 is very old, so maybe some bugs you are seeing with it
> are gone in 0.9.
>
> Regards,
>
> Fabian.
>
> Subhash Chopra wrote:
>
>
>>HI,
>>
>> We did some evaluation of mozilla M18 build on linux 7 with pipelining
>>
> ON.
>
>>The test web site which we used has 16 gifs. The sniffer used revealed that
>>mozilla uses only 1 TCP connection for fetching the html as well as the
>>embedded gifs. It first sends the GET for html and after getting the
>>
> servers
>
>>response, it concatenates the GET request for each one of the gifs and
>>
> sends
>
>>over to the web server. The web server ( in my case apache 1.3.19) prepares
>>the response by concatenating the response header and the gif data for all
>>
> the
>
>>16 gifs. so far, everything is OK.. now mozilla gets the response and it
>>
> hangs
>
>>( may be its not able to demarcate the gifs boundary).. did anyone else
>>observe the same behaviour..if yes, is it logged in bugzilla.. If its a
>>
> known
>
>>problem and nobody is working on this, i offer my help in getting it
>>better...
>>
>>Apart from this, we are working on figuring out efficient ways of secure
>>
> web
>
>>browsing with satellite as the transmission medium. If the browser/origin
>>server supports only HTTP 1.0, it would result a major overhead in terms of
>>SSL handshake for each TCP connection being set up for getting the HTML as
>>well as the embedded gifs etc
>>
>>Though HTTP 1.1 provides some respite as it supports persistent connections
>>and pipelining. We would still like it to take bit further and figure out a
>>solution which is more bandwidth effective and provides faster access.
>>This is keeping in mind that SSL handshake cant be spoofed...........
>>
>>Any thoughts??????
>>
>>Any comments................
>>
>>
>>Also we would also like to contribute to the developement of mozilla
>>
> browser
>
>>to bring it as close to the best (in terms of HTTP 1.1 compliance etc) as
>>possible........
>>
>>-Subhash
>>
>>
>> ______________
>>
>>____________________________________________________________________
>>Get free email and a permanent address at http://www.netaddress.com/?N=1
>>
>>
>>
>
>
>
>
>
> ____________________________________________________________________
> Get free email and a permanent address at http://www.netaddress.com/?N=1
>
>
