Re: Using ServiceStarter to launch a "proxy is service" service
Gregg Wonderly <[email protected]>
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <[email protected]> |
Dan Creswell wrote: > I'd say it's almost a Jini Service philosophy kind of thing - "when > programming Jini Services consider the keepalive problem, here's what's > recommended for the back-end/proxy situation, here's what's sane for the > proxy only situation" and so on. Yep, I can see it both ways. I'm just thinking more about the service registration being a two way agreement which JoinManager and the API don't really have lined up. > Feels maybe like a pattern we should write up somewhere more than a code > fix? Definately should document it some how. Not sure whether that's just text, which to date we've had a hard time using to "teach" people about Jini, it seems (not sure, just reflecting on the types of questions we get typically) or an API representation that reveals the considerations where developers would be looking. I'm also thinking about a layered JoinManager thing too, which might expose registration of services, but allow plugability of the registration entity in case ServiceRegistrar is not desired. I've still got my ServiceLookup implementation that I need to cast into an API that works for multiple types of registration entities, and so I still consider this an important issue. Gregg Wonderly -------------------------------------------------------------------------- Getting Started: http://www.jini.org/wiki/Category:Getting_Started Community Web Site: http://jini.org jini-users Archive: http://archives.java.sun.com/archives/jini-users.html Unsubscribing: email "signoff JINI-USERS" to [email protected]