Hi Lyu,

2007/11/16, Lyu Abe <[EMAIL PROTECTED]>:
> What does "local" mean for you? (for me, it means the client computer)

No, for this particular case it means on the web server (which is a
proxy between the web browser and the real demexp server). The web
server is a "server" for the web browser but a "client" for the demexp
server. ;-)

  web browser <----> web server <----> demexp server

> To summarize my thoughts:
> -To be able to use timestamps, there must be a file on the client
> computer containing the timestamp of all questions, so that they can be
> compared to new timestamps(?)

No, that "file" (more probably a memory data structure) is on the web server.

> Since I feel I'm a little bit dumb on that question, here is a test case:
> -I am a user logging to Demexp for the first time
> -Two days later, I log again: can you precisely describe what is the
> process of using timestamps in that case? (client and server sides)

Ok, I try :-)

 1. The client web browser connects to the web server;

 2. The web server connects to the demexp server. It gets the new timestamps;

 3. The web server compares those timestamps to the old ones it has
store somewhere (e.g. in memory);

 4. If some timestamps are newer, the web server gets from the demexp
server the corresponding new labels of tags;

 5. After all that steps, the web server makes the HTML page and send
it back to the client web browser.

Now, trying to be clearer :

 * In a first prototype, you can replace steps 2-4 by "* Connect to
the demexp server and always get all the tags with their labels";

 * If you really want to use timestamps, you probably won't do steps
2-4 for each new request of a web client but only after a timeout,
e.g. each 10 or 20 minutes.

Is it clearer now?


Demexp-dev mailing list

Répondre à