> you already have multiple interfaces, so thread safety must already be taken into account at the core level
Xindice only supports one Database instance at a time. You can't use 2 different servlets accessing the same DB simultaneously. You can't use a servlet and a process using the embedded interface at the same time, etc.
Also, there are internal thread safety issues in Xindice. e.g. the XUpdate code (l documented some of that in Bugzilla).
OK. Good information. That's what I was wondered.
> I guess if I don't hear otherwise, I'll assume that it's all thread-safe
On open-source mailing lists, it's never safe to assume that if you don't hear otherwise it must be so. Sometimes people know the answer but are too busy to comment...
Point well taken. Thanks for taking the time to set me straight on this one.
So then I guess to enable the possibility of simultaneous different servlets (soap, xml-rpc, etc) would be for them to coordinate with each other the use of a shared db instance. Perhaps a root XindiceServlet class that they all derive from, who supplies the database, and then everybody synchronizes on it when using it. Just thinking out loud...
Anyway thanks again..
Jim
-Terry
Jim Wissner wrote:
Hi Vladimir,
What would you think of moving your code into the main Xindice tree?
I think that sounds great. I'd be happy to move my code into the main tree. It's nice to contribute even in a small way to such a great project. The more I work with Xindice the more I like it!
I was thinking about reorganizing the xindice.server package as follow:
- org.apache.xindice.server.xmlrpc (actual servlet)
- org.apache.xindice.server.soap (your soap servlet)
- org.apache.xindice.server.webdav (the webdav servlet, but not the one from the scratchpad directory)
This looks very good. One question I've had is, as I posted earlier, are there issues with multiple servlets (like, xml-rpc and soap) running on the same database simultaneously. But now that I think about it, you already have multiple interfaces, so thread safety must already be taken into account at the core level. I'm still new to the architecture, so you'll have to forgive the stupid questions! :) I guess if I don't hear otherwise, I'll assume that it's all thread-safe.
Anyway - if you want to take my code and commit it, that's fine, since I don't have access or anything. I haven't made any updates since what I've put on my website.
The next concern for me is user authorization, but I'll save that for another thread! :)
Jim
and all the client code would go into a sample directory. With a tutorial for each access method, it would be really nice (IMO).
Any thoughts?
-Vladimir
-- Vladimir R. Bossicard www.bossicard.com
-- [EMAIL PROTECTED]
Visit www.jbrix.org for: + SpeedJAVA jEdit Code Completion Plugin + Xybrix XML Application Framework + other great Open Source Software
-- [EMAIL PROTECTED]
Visit www.jbrix.org for: + SpeedJAVA jEdit Code Completion Plugin + Xybrix XML Application Framework + other great Open Source Software
