In that case I think your best bet is what Evert suggested: split your
XML into multiple smaller, more manageable files. The splitting could
take place either on your server that generates the original XML or as
a separate process prior to saving theXML to CD. You could probably
even incorporate
Lets say...
you have 10 records,
aa
ab
ac
ad
ae
ba
bb
bc
bd
be
you could create an xml file which tells you all records that start with
a* can be fetched from a.xml
but yea, this is overly simplified.
Well, in short.. see where you can split up your xml and if its needed
create a central xml
--- In flexcoders@yahoogroups.com, "Doug Lowder" <[EMAIL PROTECTED]>
wrote:
>
> I had some of the same issues reading XML over HTTP. If your XML is
> dynamically generated by a server (via JSP, CF, ASP, etc.), you can
> do what I did, which is to essentially pass your search values as
> parame
--- In flexcoders@yahoogroups.com, Evert | Collab <[EMAIL PROTECTED]> wrote:
>
> Is there any chance you can split up the xml in multiple categories.
Or
> maybe with a 'global xml index' of some kind?
>
> Evert
Could you please explain what you mean by "global xml index"?
Wayne
--
Flexco
I had some of the same issues reading XML over HTTP. If your XML is
dynamically generated by a server (via JSP, CF, ASP, etc.), you can
do what I did, which is to essentially pass your search values as
parameters within your HTTP request and have the server pass back
only the data that match t
5 matches
Mail list logo
