Client side table mapping with extremely large data tables
Problem. Client X requested a regrouping of pages using XML DataBinding and Databound tables in MSIE for cross-browser operation.
Question . What is the best way to simulate the MSIE DataBinding function in the MSIE cross-browser (i.e. both MSIE and Firefox).
Features: Client X already gets the following using MSIE DataBinding in one web page ...
- a single-url xml dump entirely as data source (avoid server side paging and no cross-over issues)
- web page markup that no more than specifies the url of the data source (like MSIE)
- the ability to load very large tables (for example, at least 3 thousand records) without running javascript errors "from memory" or "latency" on the client side.
- the ability to do this on a regular HTML table element with interleaved rows (optional, but not required, as MSIE doesn't)
Reference Information. You probably need to familiarize yourself with MSIE DataBinding to sync this question. This MSIE feature allows you to specify a single XML data source (without any specific schema, as long as it is in a standard "table") and the browser renders the data visually and asynchronously.
The advantage of this is that the page is rendered quickly, because the page load does not wait for the entire table to fill up before showing the user some output. The rows of the table are filled in gradually.
False Start: The following actions have already been taken and rejected by Client X.
- JQuery: Works great for loading data and HTML markup with cleanliness of service, but large data sources cause latency and memory issues when rendering on the client side
- XSLT: This scares client X because it involves a lot more than just specifying the "data source" attribute on the <table> so it seems to be less user-friendly.
- Server side rendering: This is not an option because the X client religiously wants to avoid sharding the XML data or performing any "data manipulation" on the server side.
source to share
You don't really have any other options other than Javascript / XSLT and server side.
I would probably go with XSLT, the argument given against it is completely moot "because it involves much more than just specifying the" datasource "attribute in the <table> tag" - * ANY * being more complicated. and then just specify "data source".
I'm not sure, however, if the page is going to load gradually with XSLT, the spider senses indicate otherwise. Anyone?
Otherwise, you can always go with the server side option and opt out of any pagination. You will still load the page as before. As far as the browser is concerned, this is just plain html.
source to share