|
Dear all,
First, many thanks for creating and sharing this great tool which is ELOG! Our users are very happy with it!
I have few questions about inserting images into the entries.
From time to time our users insert them directly in the editor what leads to encoding the whole image in the HTML log file and the images does not appear in the attachments list. Saving and further editing of such entries slows down the whole ELOG server which uses 100% of CPU.
I'm not sure how they do it Ctrl+C & Ctrl+V, drag & drop, etc.. What I know is that if they add it using the "Insert image" action in the editor there are no problems and the images are properly listed in the attachments.
I read in the docs:
uploading or downloading an attachement file is a single request, and causes the entire file to be loaded in server memory while the request is being processed.
This is not normally a problem for the sort of short, text-mode entries ELOG is designed to support. However, if a user starts to upload or download a large attachment file (or image) over a slow link, all other users on that ELOG server will have to wait for that transfert to finish before they can access any logbook on that server. This is why there is a low limit on the size of attachments, and why ELOG should not be used to distribute large files under intensive multi-user conditions.
but I think this is not our case. Here I talk about wrongly inserting a single image of 700KiB.
So, I'm asking:
- Is the behavior that we observe something already detected? If yes, which are exactly the wrong ways of inserting the images?
- Is it fixed in newer ELOG versions?
- Is it possible to disable the wrong ways of inserting the images in order to avoid such problems?
Many thanks in advance for your help!
|