Questions about EJBSpaces Design
Status: Alpha
Brought to you by:
stabba
Menu
▾
▴
I came across this project while doing background research for a similar project I need to do for work. it seems different enough from what I expected that I thought I'd ask a few questions. Hope I don't offend.
1) Why com.stabba and not something like org.ejbspaces for the package names?
2) Why not embed reggie/outrigger/mahalo into a J2EE environment and add JNDI access in addition to the Jini discovery mechanisms, rather than writing everything from scratch? It appears from a quick browse of the CVS tree that the only access to the space will be via JNDI is that correct?
3) What is the target application here? I'm trying to build a compute farm and am not thrilled with the solutions that are available to me right now. I'm curious if that is the goal of this project.
rvs
Ronald,
1) EJBSpaces is just one project out of many possible. Many of the components should be reusable outside of the EJBSpaces project. For example, you can run a space completely local without EJB's at all.
2) Yes, I wanted a clean-sheet implementation. What you say is certainly possible and probably not too difficult (write a new space accessor for example). We're basically after an easy to deploy jar (or ear) file. For now, it's only JNDI, but when we try to pass Sun's compatability tests (out next milestone) we'll probably have to write a space accessor that uses Discovery. It should not too far a step to offer a "regular" JavaSpace as well. (But then the name EJBSpaces doesn't make much sense - see question #1)
3) You can certainly use EJBSpaces as a compute server, however our "target audience" is actually broader. Most people interested in compute-servers don't care too much about Servlet access, DataSource access, etc.
Thanks,
Bryan