Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon3.gif   per entry "expand" in threaded view, posted by Emiliano Gabrielli on Mon May 2 12:39:36 2005 
    icon3.gif   Re: per entry "expand" in threaded view, posted by Stefan Ritt on Mon May 2 13:02:58 2005 
       icon3.gif   Re: per entry "expand" in threaded view, posted by Emiliano Gabrielli on Mon May 2 13:31:18 2005 
          icon2.gif   Re: per entry "expand" in threaded view, posted by Stefan Ritt on Mon May 2 13:37:03 2005 
             icon2.gif   Re: per entry "expand" in threaded view, posted by Emiliano Gabrielli on Mon May 2 14:49:47 2005 
                icon2.gif   Re: per entry "expand" in threaded view, posted by Stefan Ritt on Mon May 2 14:51:43 2005 
                   icon12.gif   Re: per entry "expand" in threaded view, posted by Emiliano Gabrielli on Mon May 2 15:37:11 2005 
                      icon12.gif   Re: per entry "expand" in threaded view, posted by Stefan Ritt on Mon May 2 16:01:13 2005 
Message ID: 1119     Entry time: Mon May 2 13:31:18 2005     In reply to: 1116     Reply to this: 1121
Icon: Idea  Author: Emiliano Gabrielli  Author Email: AlberT@SuperAlberT.it 
Category: Request  OS: All  ELOG Version:  
Subject: Re: per entry "expand" in threaded view 
> > of course elog should remember the choice, so it will be possible to expand
> > N threads over the M total ones..
> 
> How should elog remember that? If you put this into the URL like
> 
> http://<elog-host>/<logbook>/?exp=12&exp=14&exp=18
> 
> to expand the entries 12, 14 and 18, it might work fine. But imagine that some uses
> have very long list with thousands of entries. This would make the URL very long,
> everything very slow and could even crash some browsers.
> 
> What I usually do is to not expand the list. If I click on an individual entry, I
> see then the expanded thread for that entry above that entry. But you probably
> realized this possibility already.

:-) yes I do 

A way may be using cookies, otherwise one can implement a kind o session mechanism
(using cookies or QS to pass sessid and storing user data on the server for a limited
time...)
the session method may be useful, but more difficult to implemnet, of course
ELOG V3.1.5-fe60aaf