[ome-users] Inquiry Regarding Disabled Processor.py Functionality

[josh.moore at gmx.de]

Hi Andy

processor.py uses posix signalling at the moment (os.kill(), etc.) and
so solely works on posix systems, i.e. not Windows. I'll look into
finding a higher-level library to replace the code in
OmeroPy/src/omero/processor.py to make it compatible with Windows,
which you're also welcome to do. Just be aware: it's not a single
location that has to be changed, but the entire module.

At the same time, can you tell us what it is you are trying to do
with processor.py? Perhaps we know another way to accomplish the same
task.

Best wishes,
~Josh. 


Carl, Andrew F (AS) writes:
 > Josh,
 > Thanks for the where/how info. Seeing that the WinXP platform is
 > "not the preferred platform of choice for production servers", could you
 > please be more specific to facilitate the development of a workaround
 > since winxp is the only choice for us. Are there any documented error
 > details or useful documentation?
 > 
 > Thanks,
 > Andy
 > 
 > -----Original Message-----
 > From: josh.moore at gmx.de [mailto:josh.moore at gmx.de] 
 > Sent: Friday, August 14, 2009 1:06 AM
 > To: Carl, Andrew F (AS)
 > Cc: OME-Users OME-Users
 > Subject: [ome-users] Inquiry Regarding Disabled Processor.py
 > Functionality
 > 
 > 
 > Hi Andy,
 > 
 > processor.py is deactivated by not including the line:
 > 
 >   <server-instance template="ProcessorTemplate" index="0"/>
 > 
 > in windefault.xml here:
 > 
 >  
 > https://trac.openmicroscopy.org.uk/omero/browser/branches/Beta4.0/etc/gr
 > id/windefault.xml#L46
 > 
 > Just adding it, however, will not work as expected. Processor.py
 > launches separate executables, functionality which to date has only been
 > implemented for Posix (Unix, Linux, Mac) OSes.
 > 
 > Cheers,
 > ~Josh.
 > 
 > 
 > Carl, Andrew F (AS) writes:
 >  >
 >  > The windows install web page states that one of the current
 > limitations  > on the windows platform install of Omero, is that the
 > "processor.py  > functionality is currently disabled". Two questions:
 >  >
 >  > A) Why
 >  > B) Where/how
 >  >
 >  > I have been unable to locate the where & how. Please advise.
 >  >
 >  > Thanks,
 >  > Andy