Hi list,

About CSTables activity ... The project stopped after a beta release 
for PyTables 1.0. Simply I had no time to continue the development. 
Moreover, my current job was not related to these themes anymore. 

However, I was thinking in a release for PyTables 2.0, considering 
that it will be a more stable release with less API changes in the near 
future, etc. And I'm still thinking. It will help if someone offers 
collaboration (developing, contracting, etc.) to continue the 
development. In that case, probably it will be a new release with an 
Open Source license.

This is a link to the CSTables 1.0 beta announce, for those who don't 
know his features:

http://sourceforge.net/mailarchive/message.php?msg_id=11841440

If someone is interested in the new release, please e-mail me.

Regards,

Andreu Alted


----Mensaje original----
De: [EMAIL PROTECTED]
Recibido: 07/03/2007 3:20
Para: <pytables-users@lists.sourceforge.net>
Asunto: Re: [Pytables-users] Is cstables still active?

On Tuesday 06 March 2007 16:08, Mike Romberg wrote:
> >>>>> " " == Joshua J Kugler <[EMAIL PROTECTED]> writes:
>      > I was looking through the PyTables archives a couple days 
ago,
>      > and saw an announcement for CsTables.  As we're going to be
>      > using PyTables in somewhat of a client/server environment 
soon,
>      > something like CsTables would be great.  If it is no longer
>      > active, what do others use for client/server access to 
pytables
>      > data?  Shared drive mounted read-only (samba, NFS)?  SOAP?
>      > XML-RPC?  Something else?
>
>   I have a cstables "like" implementation using Pyro instead of
> twisted.  It used to work with version 1.3 of pytables.  I have no
> idea if it still works or not with the newer pytables.  If you are
> interested, I could send you a copy.

Hmm...pyro.  Hadn't thought about that.  I guess Pyro might be an 
option.  The 
only thing is: I'm mainly looking for concurrency control, which is 
what 
CSTAbles advertised.  I might being doing data acquisition in 
multiple 
processes or threads, and didn't want to have to worry about 
concurrency 
myself.  Maybe I'll just whip up some modules that are multithreaded 
and use 
Fazil Majid's rwlock.py[1] module to keep them from stepping on each 
other.

Please send along your Pyro modules.  I'm sure they'd be of great help 
to me.

[1] http://www.majid.info/mylos/weblog/2004/11/04-1.html

-- 
Joshua Kugler                           
Lead System Admin -- Senior Programmer
http://www.eeinternet.com
PGP Key: http://pgp.mit.edu/  ID 0xDB26D7CE
PO Box 80086 -- Fairbanks, AK 99708 -- Ph: 907-456-5581 Fax: 907-456-
3111

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to 
share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.
php&p=sourceforge&CID=DEVDEV
_______________________________________________
Pytables-users mailing list
Pytables-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pytables-users





Ahora también puedes acceder a tu correo Terra desde el móvil.
Infórmate pinchando aquí.



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Pytables-users mailing list
Pytables-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pytables-users

Reply via email to