Steve Jones wrote: > I was thinking about using a space for what I'm coding, but I thought > I'd try it out just using the bits in the standard Java language. The > biggest challenge I'm facing is eventing, which a space would have > made easier. > > > > > Javaspaces programming allows software to focus specifically on the data > > processing. It also allows programming in the small as the predominent > mode. As > > with any transactional services, it is still possible to create circular > wait. > > And I still can't get over the lack of elegance of public variables.
This is caused by an implementation detail being made visible. What is at issue, is that Entry objects are stored in most javaspaces as MarshalledObject wrapped values, not live objects. There's a whole string of dependencies that fall out of this decision to protect the space and the application from codebase contamination and the lost codebase issues. I've been working on http://griddle.dev.java.net as some investigation into separating keys from data, and using a matching method in live objects. It's an interesting bit of stuff. There are pros and cons both ways. Gregg Wonderly Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/service-orientated-architecture/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
