Paging WebService response.

[san_marcus]

Hi, this time am working in a webservice for a national company in my country, so the web service calls a method and this query goes to the server bringing a litlle more than 50.000 registries in one only response, it happens in asincronohus method, so am pretty sure no new data will be loaded while am showing the 50.000 registries, of course the browser freeze when try to load so many registries, my main question is what can I do to paging al those record and only show 300 registries per page.. and of course, the 4 ussual buttons, Start, Back, Forward,Last. please any help would be good, some people have already told me that I must load this registry in a temporal memory, I am pretty sure, I don´t know how to do that?, am working with java 1.5 and my sdk is jdeveloper 10.1.3.5

[Norm]

If sending the full number of "registries" makes for too large a file to view, then it would seem you need some software to break it up into smaller pieces.
Perhaps you could use an applet to display the pieces and have the applet communicate with code on the server to move the "view" around on the underlying "registries"

[san_marcus]

the client does not wish to use applet.. (#$")#

[Norm]

Then its special code on the server to send the browser pieces of the whole. I don't know how the browser tells this code to move to the next or the previous view. That would require links within the page with the current piece.

[san_marcus]

thanks for your quick response, the matter here is the browser reads from the server, but no matter wich browser the client use, all of them freeze trying to read all the registries, my question is ... will be a good idea to load all this data by http into a heap or something like that or is there any way to for example, execute a first query than request 10.000 registrys and if the client press. next then send another request for the next 10.000 and so on, or wich could be the best way to handle this.. please give me a suggest because this is my first time dealing with some thing like it.

[Norm]

Don't let the browser directly read the whole of the registries. Have it go to some other code that will be able to pick up the part that the user wants to see next. This could involve servlets or cgi-bin or PHP or ???

[san_marcus]

the question is .. "Have it go to some other code " that is what I want" to Find

[Norm]

That could be the part that you have to write.

[Tolls]

You'll need to change the webservice to supply it with an offset.
That's how paging works.
You tell the thing that provides the data "I want this data, starting from this row, with this number of rows".