Results 1 to 3 of 3

Thread: How to implement multithreaded parsing xml

  1. #1
    Join Date
    May 2009
    Posts
    18

    How to implement multithreaded parsing xml

    I can organize a multithreaded parsing xml document. For example by clicking on the button, I called two classes. One gets the desired site. The second is waiting for some time, gets the index of this site and it reads the correct piece of xml document.

  2. #2
    Join Date
    Dec 2008
    Posts
    63

    Re: How to implement multithreaded parsing xml

    If you use the SAX parser you can for each tag to use a separate thread ... but, again, then collect all the information in one model ... and unlikely as it would expedite the process.

  3. #3
    Join Date
    Dec 2008
    Posts
    99

    Re: How to implement multithreaded parsing xml

    XML elements have to be properly nested; in particular, the opening and closing tags of different elements must not overlap. In other words, an element's opening and end tags must reside in the same parent.The document is also derived from a full copy of each individual Record element from the input file. So that object is distinct for each task, and you have no problem with synchronization there either.

Similar Threads

  1. How to use XML Parsing using PHP
    By LasitMalinga in forum Software Development
    Replies: 4
    Last Post: 05-10-2011, 02:33 PM
  2. Stop a multithreaded server
    By Remedy in forum Software Development
    Replies: 5
    Last Post: 02-02-2010, 05:46 AM
  3. Is Age of Empires a multithreaded game
    By Dhruv in forum Video Games
    Replies: 3
    Last Post: 18-06-2009, 09:53 AM
  4. Replies: 0
    Last Post: 09-05-2009, 12:48 PM
  5. Parsing in C++
    By Elijah in forum Software Development
    Replies: 4
    Last Post: 20-04-2009, 11:39 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,714,105,864.91007 seconds with 16 queries