multipart/mixed html's

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Niels Berkers

    #31
    Re: multipart/related <-> persistant

    Hi Manuel,
    [color=blue]
    > Anyway, back to the original thread, persistent HTTP connections are
    > precisely to avoid many simultaneous connections to the same server and
    > the browser uses the same HTTP connection during the same page request .
    >
    > If you are concerned that the same user monopolizes the same connection
    > for many different consecutive page requests, just reduce the keep alive
    > timeout to 1 or 2 seconds and the connection will not last between
    > consecutive normal page browsing.
    >[/color]
    Ok, when using a persistent connection, apache still as to handle all the
    hits.
    maybe up to 200 for just 1 page. When I have multipart/related doc apache
    would have to handle just one hit and push out a block of data.
    In the server multipart/related docs also have to be faster, when you can
    put all
    if the content in one file, it takes less IO , than gathering all info for
    each user.
    On a peek load, i think, it easier just to push out data in one block,
    instead of
    100 small blocks. Specialy when you're talking about small files ( less than
    1500 mtu incl header ) On the other hand, i don't exactly know who a
    browser/apache handles a KeepAlive.
    [color=blue]
    > Anyway, KeepAlive is not the recommended solution either. My original
    > recommendation is to serve images with a separate dedicated HTTP server
    > like thttpd .[/color]

    Yep, an that's what we're gona use 8-)


    Regards

    Niels Berkers



    Comment

    • Niels Berkers

      #32
      Re: multipart/mixed html's

      > If it doesn't, it doesn't. Why don't you just stick to the traditional[color=blue]
      > solutions that are widely supported?[/color]

      Maybe I just hard headed 8-)
      Just have to try everything myself...


      Regards

      Niels Berkers



      Comment

      • Niels Berkers

        #33
        Re: multipart/mixed html's

        I think i'd cleared that one
        earler on in the thread...

        Regards


        Niels Berkers


        Comment

        • CountScubula

          #34
          Re: multipart/mixed html's

          "Niels Berkers" <meel_me_niet@h otmail.com> wrote in message
          news:103fc0fo1q cqk1f@corp.supe rnews.com...[color=blue]
          > Hi,
          > i'd like to host my web pages using multiparts to reduce the number of
          > hits on the server.
          > i know this isn't a real PHP subject, but i'll try it anyway.
          > i've been searching the web for solutions and examples with no succes.
          > does anybody know a good starting point
          > hints / tips are also welcome
          >
          > Regards
          >
          > Niels Berkers
          >
          >[/color]

          Most browsers do not support multipart (and dont ask me why, or which)

          However, I do understand what you are talking about, is your question more
          of:

          I do not like mutliple connections for each resource on and including the
          page, is there another way?

          if so, then yes, turn on persistant connections on your webserver, thus one
          TCP connection is made, and several resources are reqested across it. still
          apears as several hits in the log, but only one TCP connection.
          Also, give apearance of faster site, due to lack of making and breaking
          connections.

          --
          Mike Bradley
          http://www.gzentools.com -- free online php tools


          Comment

          • Manuel Lemos

            #35
            Re: multipart/related &lt;-&gt; persistant

            Hello,

            On 02/24/2004 05:41 PM, Niels Berkers wrote:[color=blue][color=green]
            >>Anyway, back to the original thread, persistent HTTP connections are
            >>precisely to avoid many simultaneous connections to the same server and
            >>the browser uses the same HTTP connection during the same page request .
            >>
            >>If you are concerned that the same user monopolizes the same connection
            >>for many different consecutive page requests, just reduce the keep alive
            >>timeout to 1 or 2 seconds and the connection will not last between
            >>consecutive normal page browsing.
            >>[/color]
            >
            > Ok, when using a persistent connection, apache still as to handle all the
            > hits.[/color]

            Yes, but the same HTTP connection is reused to make many requests of the
            same page. It is not like it will open 200 connections to fetch 200
            images. That is the point of Keep-Alive.


            --

            Regards,
            Manuel Lemos

            PHP Classes - Free ready to use OOP components written in PHP
            Free PHP Classes and Objects 2026 Versions with PHP Example Scripts, PHP Tutorials, Download PHP Scripts, PHP articles, Remote PHP Jobs, Hire PHP Developers, PHP Book Reviews, PHP Language OOP Materials


            PHP Reviews - Reviews of PHP books and other products


            Metastorage - Data object relational mapping layer generator

            Comment

            Working...