Re: [Zope-dev] Re: AdaptableStorage
Hi Shane I have been thinking about this last night. I think you should provide some sort of out of band signalling method. But given that Adaptable Storage sits below ZODB, which sit's below Zope, I feel that the signalling method should be directed at the lowest level. This means that method doesn't need to be exposed to ZODB, and if people use ZODB without Zope they can use Adaptable storage and not need Zope to perform the signalling through a URL. (A Zope front end could then use it, or anything else for that matter) I would suggest a something like a named pipe, and do a blocked read from a python thread (would this be portable and can you actually do that ;-). Then use a simple protocol of sending the path to the file that has been changed. (That way you also get a FIFO queue of events.) You could make it that if the path is a directory then everything under could be treated as changed. Just 2c See ya Tim Hoffman On Wed, 2003-01-22 at 20:06, Shane Hathaway wrote:
On Wed, 22 Jan 2003, Chris Withers wrote:
I think this is as "such is life" problem. Provided AdaptableStorage provides some way (exposed url?) for an external process to say that things have changed, I think that's the best form of flexibility we can provide.
I think I'll provide such an URL, then. Thanks for going over this.
Shane
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
DISCLAIMER: This email, including any attachments, is intended only for use by the addressee(s) and may contain confidential and/or personal information and may also be the subject of legal privilege. Any personal information contained in this email is not to be used or disclosed for any purpose other than the purpose for which you have received it. If you are not the intended recipient, you must not disclose or use the information contained in it. In this case, please let me know by return email, delete the message permanently from your system and destroy any copies. Emails and their attachments may be interfered with, may contain computer viruses or other defects and may not be successfully replicated on other systems. All attachments are opened at the recipient's risk.
THoffman@indtech.wa.gov.au wrote:
Hi Shane
I have been thinking about this last night.
I think you should provide some sort of out of band signalling method. But given that Adaptable Storage sits below ZODB, which sit's below Zope, I feel that the signalling method should be directed at the lowest level. This means that method doesn't need to be exposed to ZODB, and if people use ZODB without Zope they can use Adaptable storage and not need Zope to perform the signalling through a URL. (A Zope front end could then use it, or anything else for that matter)
I would suggest a something like a named pipe, and do a blocked read from a python thread (would this be portable and can you actually do that ;-). Then use a simple protocol of sending the path to the file that has been changed. (That way you also get a FIFO queue of events.) You could make it that if the path is a directory then everything under could be treated as changed.
That would be pretty cool, since it's easy for scripts to add to the queue, and it gives you plenty of granularity. It wouldn't work under Windows, though, AFAIK. Maybe on Windows we could call back to a network socket that accepts the same kind of data. (Sorry for taking so long to get back to you. I got swamped.) Shane
Shane Hathaway wrote:
That would be pretty cool, since it's easy for scripts to add to the queue, and it gives you plenty of granularity. It wouldn't work under Windows, though, AFAIK. Maybe on Windows we could call back to a network socket that accepts the same kind of data.
Oops, I meant "fall back to a network socket". Shane
participants (2)
-
Shane Hathaway -
THoffman＠indtech.wa.gov.au