hi again,

we have been doing a bit of stress testing for Elog. The most important 
thing we found is that Elog stops responding when a user uploads a large 
attachment (we used a 240 Mb attachment). 

Is it possible to add a flag in the configuration file, to specify the 
maximum size of an attachment?

Bartjan Wattel

Using the COMMENT feature to add guidance to an ATTRIBUTE works great, but
is it possible to add a TOOLTIP <ATTRIBUTE> = so as to save screen space? 
For a complex entry form it is desireable to try and have everything in a
single window and this, I think, would help.

Thanks

> Using the COMMENT feature to add guidance to an ATTRIBUTE works great, but
> is it possible to add a TOOLTIP <ATTRIBUTE> = so as to save screen space? 

Where should the tooltip appear? In the entry form or when an entry is
displayed, or even in the tabular listing? I can put a title arround the
attribut names such as

<div title="Please enter some subject here">Subject:</div>

which gets interpreted by most browsers as a tooltip. However it's not
apparent to the user that leaving the cursor on top of "Subject" opens a
tooltip, especially since the cursor is displayed as the text cursor (vertical
bar), not as an arrow over the attribute. Do you have a link to a public web
page which uses tooltips?

> For a complex entry form it is desireable to try and have everything in a
> single window and this, I think, would help.

Aiming for running elog on you PDA? Let me know if you succeed...

> > Using the COMMENT feature to add guidance to an ATTRIBUTE works great, but
> > is it possible to add a TOOLTIP <ATTRIBUTE> = so as to save screen space? 
> 
> Where should the tooltip appear? In the entry form or when an entry is
> displayed, or even in the tabular listing? I can put a title arround the
> attribut names such as
> 
> <div title="Please enter some subject here">Subject:</div>
> 
> which gets interpreted by most browsers as a tooltip. However it's not
> apparent to the user that leaving the cursor on top of "Subject" opens a
> tooltip, especially since the cursor is displayed as the text cursor (vertical
> bar), not as an arrow over the attribute. Do you have a link to a public web
> page which uses tooltips?
> 
> > For a complex entry form it is desireable to try and have everything in a
> > single window and this, I think, would help.
> 
> Aiming for running elog on you PDA? Let me know if you succeed...

In the Entry form I am thinking, as this is when most people need some help. 
Perhaps the user could be clued in with a "Mouse-over each attribute for Help"
COMMENT at the top.

As for the PDA, no, it's just that some people around here get confused if they
have to scroll down.  Not a big thing . . . ;-> Hmmm, PDA . . . 

Ok, I added the option

Tooltip <attribute> = ...

I apply the HTML "title" tag to the whole table row, so the tooltip appears on the
whole line, not only the attribute name. I guess this is much more intuitive. Give
it a try. New version under CVS and available as a snapshot.

> Is it possible to add a flag in the configuration file, to specify the 
> maximum size of an attachment?

I implemented a "max content length = xxx" flag, which defaults to 10MB. If an
attachment is larger, an error gets displayed. The problem is that elogd can
only send the error message to the browser *after* it received the whole
request, so it has to "drain" the 240 MB first, which could take quite some
time on a slow connection.

Alternatively, I can cut the connection to the browser immediately, since the
HTTP header contains the content length after the first ~500 bytes, but in
that case the browser only shows a message box "Document contains no data"
which gives the user noe clue of what's wrong.

Anyhow the biggest problem of elog in high stress environments is that it's
single threaded. So if someone issues a search in a large logbook, it could
take some time, in which elog cannot respond to other requests. Maybe I will
find time in the future to make elog multithreaded, but certainly not in the
near future.

Something to add to the wishlist:

- Type <attribute> = user

This would define an attribute as being of the type "user" which is a list
of login id's as defined in a password file or on the "Login user =" line. 
In a dataentry form the presence of this ATTRIBUTE would result in a
picklist of loginid's and/or fullnames.

Acknowledged. Added your vote to the wishlist.