The problem is the same as in #98. We can have a configurable limit of tables/dict/array which we render. At the moment c.java reads everything into buffer and then parses the response. So there are 2 possible way to implement this:
(A) (simple one) read everything; but limit during rendering. So we are saving on creation of Swing objects
(B) (more complex) rework c.java to parse response during rendering. If we are parsing top level table/dict/list, we can start skipping some data in end of configurable limit. I think the table is encoded in the stream as list of column names, the first column, the second column, and etc. So in this option we need to "selectively" read and parse the stream
The problem is the same as in #98. We can have a configurable limit of tables/dict/array which we render. At the moment c.java reads everything into buffer and then parses the response. So there are 2 possible way to implement this: (A) (simple one) read everything; but limit during rendering. So we are saving on creation of Swing objects (B) (more complex) rework c.java to parse response during rendering. If we are parsing top level table/dict/list, we can start skipping some data in end of configurable limit. I think the table is encoded in the stream as list of column names, the first column, the second column, and etc. So in this option we need to "selectively" read and parse the stream