@MSGID:
<eccd921a-8b64-46fe-a2ce-2aed142df6abn@googlegroups.com> aff0b1d2
@REPLY:
<694abf6d-9e11-41a8-a663-73c407c901cen@googlegroups.com> 3e832e74
@REPLYADDR Larry Serflaten <serflaten@gmail.com>
@REPLYTO 2:5075/128 Larry Serflaten
@CHRS: CP866 2
@RFC: 1 0
@RFC-References:
<0c640188-cdf2-421e-aca2-583457644423n@googlegroups.com> <d0dfac9e-d413-490b-a595-fb2fcde550aan@googlegroups.com>
<24c250df-8e59-4af9-b5bf-d17f6a92a6e4n@googlegroups.com> <20230414171132.00006d23@mvps.org.invalid>
<5cf1be47-7a74-42fa-b012-9e0c167ae58en@googlegroups.com> <1c082c0f-fad1-4a99-834b-22db0cc3c815n@googlegroups.com>
<20230822174909.00004e84@mvps.org.invalid> <d8705cd6-a647-4f5c-92e7-4746e79a5448n@googlegroups.com>
<20230825113749.00003ea6@mvps.org.invalid> <20230825113913.000017cb@mvps.org.invalid>
<877e2be8-725d-4849-9c7c-4ea2adc83303n@googlegroups.com> 1@paganini.bofh.team>
<6aa51ffe-f4a3-46a4-a793-f971c42d26f5n@googlegroups.com> 1@paganini.bofh.team>
<bde707de-6b62-41b9-b198-a25c135762d2n@googlegroups.com> 1@paganini.bofh.team>
<f4046b66-7001-40fe-8667-a246c4403dcdn@googlegroups.com> <oFKdncM5N4x9eGz5nZ2dnZfqn_idnZ2d@giganews.com>
<965cbf88-2aa7-42ea-962c-42f6c42544a9n@googlegroups.com> <694abf6d-9e11-41a8-a663-73c407c901cen@googlegroups.com>
@RFC-Message-ID:
<eccd921a-8b64-46fe-a2ce-2aed142df6abn@googlegroups.com>
@TZUTC: -0700
@PID: G2/1.0
@TID: FIDOGATE-5.12-ge4e8b94
 Accu Backup wrote:

 > Thanks all for the added info. Out of these two options, I
think reading the file in binary chunks would be my best option. As I
am reading the file in a chunk... can I detect when I hit a closing
parent tag?

 Not during the disk read operation. You grab some round number of
bytes (4-8MB) then parse the raw data in memory. You keep track of how
much you have parsed so that your next disk read operation begins where
your parsing left off.

This old post (from 1999!) may help, do search this group for other examples:
https://groups.google.com/g/microsoft.public.vb.general.discussion/c/qWKpXPzdRbI
/m/g9EEXOqxsswJ

LFS
--- G2/1.0
 * Origin: usenet.network (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441