Context Navigation

← Previous Change
Ticket History
Next Change →

Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.

Changes between Version 1 and Version 7 of Ticket #7902

Timestamp:: 03/07/13 11:09:24 (11 years ago)
Author:: jmoore
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #7902
- Property Cc bpindelski jkoetsie@… added
- Property Milestone changed from OMERO-Beta4.4 to Future

Ticket #7902 – Description

v1	v7
12	12	* OmeroSearch: Search messages should likely contain the entire serialized Lucene `Document` along with links to any files on disk which need processing. This would allow SearchBridges to remain functioning largely unchanged while upholding the single-writer requirement of Lucene.
13	13	* !PixelData: Each time a request is made for an image pyramid that does not yet exist, the Pixel graph should be sent to an MQ instance which has access to the proper image files. From these, a pyramid file (e.g. `/OMERO/Pixels/001_pyramid`) should be generated. Optimally, no processing would take place if the pyramid has been generated in the mean-time.
14		* OmeroFs: A monitoring service provides FS-level events about files which have been created in configured directory. A second dropbox client receives these events and possibly kicks off the import of data. The DropBox client has extensive threading/waiting configuration to properly handle eventualities that may be better served by an MQ.
	14	* OmeroFs: A monitoring service provides FS-level events about files which have been created in configured directory. A second dropbox client receives these events and possibly kicks off the import of data. The DropBox client has extensive threading/waiting configuration to properly handle eventualities that may be better served by an MQ. (See #1429)
15	15	* OmeroScripts: `Processor-0` icegridnode servers accept jobs to be run in sub-processes. At the moment, these are unbounded queues which can quickly overwhelm the server.
16	16	* LDAP Plugin (#7745): When users or groups are synchronized from LDAP, all members of those groups along with administrators should be notified by email. Since this could be a large number of emails to send, this should happen asynchronously.