Have a background process:
foreach query("select id,points from table where encoded = NULL limit 1000"):
$encoded = encode($points)
execute("update table set encoded = $encoded where id = $id");
end
And keep running it until all points are encoded.
(of course the above is only pseudo code)
... then the 'output' page, just reads the encoded line and outputs
that in the XML file.
You offset a bit of database storage space (the encoded column), for
not having to encode 'on the fly'. All ultimately to reduce the amount
of work done in creating the XML file, and also making it smaller -
saving bandwidth - and improving page speed.
(This system is ideal for 'write once, read many' systems)
On 23/06/2009, Santosh <[email protected]> wrote:
>
> Dear Barry,
>
> Here is the URL for my application.
> http://www.wetlandsofindia.org/kerala/sample.htm
> Here is the URL for one query to the database
>
> http://www.wetlandsofindia.org/kerala/test.php?district=Palakkad&block=Alathur&panchayat=Alathur&munpanval=panchayat&size=1
> This will give you some result. Do I encode here in XML generating
> code? When you query at district level, it generates huge XML and
> which takes longer time to load or sometimes it doesnt load. I am not
> getting where to encode exactly.
>
>
> Santosh
>
> >
>
--
Barry
- www.nearby.org.uk - www.geograph.org.uk -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Maps API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Maps-API?hl=en
-~----------~----~----~----~------~----~------~--~---
