server implementation on paging grid

[haibin]

Hi,

I'm looking at the Paging Grid example and have a question on the server implementation.

In ExampleServiceImpl class

private List<Post> posts;

public PagingLoadResult<Post> getPosts(final PagingLoadConfig config) {
    if (posts == null) {
      loadPosts();
    }
 
    // ignore the rest
}

I thought posts will always be null every time a new thread is instantiated. In my own implementation, class variables do get set to null ever time. But it seems to be working fine in the demo explorer. Any idea why?

[vanderbill]

look the code in examples, there are server side code paging implementation

[haibin]

Yes, I code I posted above is from the examples.

[EagleEye666666]

Yes, I code I posted above is from the examples.

I would like to help but i did not get ur question. Just not understanding it.

[haibin]

My understanding is if servlet is started in a new thread, then

if (posts == null)

will always be true. So loadPost() will be called every time when users click on Next Page on the paging tool. Obviously it should not be the case. What's wrong with my understanding?

[gslender]

My understanding is if servlet is started in a new thread, then

if (posts == null)

will always be true. So loadPost() will be called every time when users click on Next Page on the paging tool. Obviously it should not be the case. What's wrong with my understanding?

Servlets are session based - so this only happens per client instance, not per request.

[haibin]

I see. Thanks for your help.

But where can I see those codes that handle sessions? I was looking for something like

this.getThreadLocalRequest().getSession();

in the ExampleServiceImpl.java

[gslender]

ExampleServiceImpl extends RemoteServiceServlet, which extends HttpServlet

This is a fundamental Servlet function where data is persistent.

Read this -> http://www.novocode.com/doc/servlet-.../chapter1.html