Re: [Exist-open] some "conclusions"

[Darren G. <da...@on...>]

Manuele,
Thank for raising those points. We want very much to migrate to eXist
from Tamino, but I'm afraid your points #2 and #3 prevent eXist from
being used in any sort of mission-critical or robust business environment.
Hopefully some fixes for those are forthcoming.

Cheers,
Darren

Manuele Simi wrote:
> Dear all,
> after three days of experimentations in using eXist (1.0rc) from a WSRF
> service, I would like to share with the list some issues. 
> The following is a list of some points/limitations I have seen in my
> experiments and that can influence my code:
>
> 1) It is not possible to backup the database in the same time that
> someone is writing/deleting resources
> 2) If the database is not properly shutdowned, it is possible that it
> becomes corrupted and the only solution is to store again all the
> content
> 3) Two threads that store resources at the same time in the same
> collection can cause a database corruption, so using locking mechanisms
> here is good point
>
> These points are not real limitations for me. I can go over them.
> I list them here just to know if I'm right (and this meas that others
> encountered them in their experiences) in order to proceed with my
> project by taking into account them or if it is possible that these
> situations are caused by the way in which I use eXist.
> What do you think about?
> Any feedback is appreciated.
>
> regards,
> manuele
>
>
> -------------------------------------------------------------------------
> 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
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
>