xml parsing (SAX) buffer limits

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

    xml parsing (SAX) buffer limits

    Is there any good documentation of what sort of input buffer limits there
    are for the expat parser used by PHP? I found out (by accident) that my
    webhosting service's version has a 1024 byte limit.


  • Amir Khawaja

    #2
    Re: xml parsing (SAX) buffer limits

    sinister wrote:
    [color=blue]
    > Is there any good documentation of what sort of input buffer limits there
    > are for the expat parser used by PHP? I found out (by accident) that my
    > webhosting service's version has a 1024 byte limit.
    >
    >[/color]
    That sounds about right. You also have to remember that Expat uses
    callback functions and reads data in blocks. This gives it an advantage
    over DOM when reading large files. As long as your XML is file valid you
    should not have problems.

    --
    Amir Khawaja.

    ----------------------------------
    Rules are written for those who lack the ability to truly reason, But
    for those who can, the rules become nothing more than guidelines, And
    live their lives governed not by rules but by reason.
    - James McGuigan

    Comment

    • sinister

      #3
      Re: xml parsing (SAX) buffer limits


      "Amir Khawaja" <amir@gorebels. net> wrote in message
      news:PQyEb.2986 1$m83.9891@fed1 read01...[color=blue]
      > sinister wrote:
      >[color=green]
      > > Is there any good documentation of what sort of input buffer limits[/color][/color]
      there[color=blue][color=green]
      > > are for the expat parser used by PHP? I found out (by accident) that my
      > > webhosting service's version has a 1024 byte limit.
      > >
      > >[/color]
      > That sounds about right. You also have to remember that Expat uses
      > callback functions and reads data in blocks. This gives it an advantage
      > over DOM when reading large files. As long as your XML is file valid you
      > should not have problems.[/color]

      Thanks for your reply.

      It was a problem insofar as the code that used the results assumed that
      there would never be two blocks of character data in a row.

      -S


      Comment

      Working...