<br><br><div><span class="gmail_quote">On 8/22/08, <b class="gmail_sendername">Andrew Milton</b> <<a href="mailto:akm@theinternet.com.au">akm@theinternet.com.au</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
+-------[ David Bear ]----------------------<br><br>| It seems to me that it could be usefull to have a zope method for passing<br> | python pickles to external processes through a unix domain socket. My thinking<br> | was to use this as a means to abstract a data base connection. Yes, I know<br>
| there are zsql methods, sqlalchemy and other products to do this. But my<br> | thought was to have a generilzed method for just passing a pickle to an<br> | external process that could do anything with it. Perhaps it could pass a pickle<br>
| to a queue that would handle the pickle if the site need some high volume<br> | handling of data.<br> |<br> | Then one could have another python process listening on the socket -- ready to<br> | receive pickles for zope.<br>
<br><br>Isn't this called ZEO? d8)<br><br></blockquote></div><br>ZEO could be a model for this - but ZEO stores the pickles to zodb. What if I wanted to queue the pickle up and take some kind of long term processing action on it? Store it in a network file system -- which may have a high write latency to, put it in a data base for which there were no zope connectors, etc.<br>
<br clear="all"><br>-- <br>David Bear<br>College of Public Programs at ASU<br>602-464-0424