I used JSON in a map application in exactly the same way you are (agent/getallentries). I built a prototype in php and moved it to domino. It worked great in php. But because of the need for an agent, was slow in domino. The ReadViewEntries and XML approach, albeit more complicated, was faster than the agent with JSON.
is much easier to handle with eval() than processing xml from a view of longitude, latitude, site number, site name, etc. But the performance hit was too much.
Do you find that there's not a noticeable difference between rendering view data with ?ReadViewEntries and the agent? Or do you just accept the performance loss in favor of the implementation benefits? Or is there some other secret (servlet/agent manager tuning) that I'm missing?
I used JSON in a map application in exactly the same way you are (agent/getallentries). I built a prototype in php and moved it to domino. It worked great in php. But because of the need for an agent, was slow in domino. The ReadViewEntries and XML approach, albeit more complicated, was faster than the agent with JSON.
My JSON feed of
[["1650450.39664552","-1950228.23368166","7107","BWI-Parkway","41935", 0],
["1373824.13000324","-2246882.14520136","7273","Jamestown-Falconer","42100", 0]];
is much easier to handle with eval() than processing xml from a view of longitude, latitude, site number, site name, etc. But the performance hit was too much.
Do you find that there's not a noticeable difference between rendering view data with ?ReadViewEntries and the agent? Or do you just accept the performance loss in favor of the implementation benefits? Or is there some other secret (servlet/agent manager tuning) that I'm missing?
Cool stuff though.