(Migrated) zato with pytables

(This message has been automatically imported from the retired mailing list)

For testing purposes I’m going to play with pytables and if results ok I
will use it to query my data in zato services . The topic here is how I can
access to hdf5 files to be managed by pytables. I know that those files
will be server specific, so they need to exist in the pc that zato server
service is running, otherwise a shared access like using pydap is needed to
access the hdf5 files with pytables. maybe with zato we can find a way to
integrate this wonderful library as an alternative to sql db outgoing
connection for manipulating large datasets.
Maybe zato can integrate this library as a service mixin like
OpenERPService using pytables for managed local files configured in redis
or using pydav to access remote shared files served by uwsgi like propose
pydav
All of this are ideas that could be implemented to make zato a better ESB

there is actually one protocol for do this kind of stuffs named opendap and
it’s python implementation named pydap http://www.pydap.org, pydap have a
plugin for hdf5 files and this is what can be used to query the pytables
hdf5 files, this create a wsgi server that can be used to query the files

On Tue, Feb 4, 2014 at 2:48 PM, Dariusz Suchojad dsuch@zato.io wrote:

On 01/30/2014 02:28 AM, Axel Mendoza Pupo wrote:

Maybe zato can integrate this library as a service mixin like
OpenERPService using pytables for managed local files configured in
redis or using pydav to access remote shared files served by uwsgi like
propose pydav
All of this are ideas that could be implemented to make zato a better ESB

I thought about it as well some time ago but didn’t quite know how to
deal with the fact that a PyTables database cannot be accessed by
multiple clients (threads or processes) simultaneously.

Is there anything in PyTables that could accept HTTP connections from
Zato and that would be responsible for connections serialization?

On 01/30/2014 02:28 AM, Axel Mendoza Pupo wrote:

Maybe zato can integrate this library as a service mixin like
OpenERPService using pytables for managed local files configured in
redis or using pydav to access remote shared files served by uwsgi like
propose pydav
All of this are ideas that could be implemented to make zato a better ESB

I thought about it as well some time ago but didn’t quite know how to
deal with the fact that a PyTables database cannot be accessed by
multiple clients (threads or processes) simultaneously.

Is there anything in PyTables that could accept HTTP connections from
Zato and that would be responsible for connections serialization?

On 01/30/2014 02:28 AM, Axel Mendoza Pupo wrote:

Maybe zato can integrate this library as a service mixin like
OpenERPService using pytables for managed local files configured in
redis or using pydav to access remote shared files served by uwsgi like
propose pydav
All of this are ideas that could be implemented to make zato a better ESB

I thought about it as well some time ago but didn’t quite know how to
deal with the fact that a PyTables database cannot be accessed by
multiple clients (threads or processes) simultaneously.

Is there anything in PyTables that could accept HTTP connections from
Zato and that would be responsible for connections serialization?