Hi Freeman,
> Is this still a Stringification-based approach?
Yup, The same stubs & skels are used for all instances of the same Home &
Remote.
> I really don't want to make this a Jini vs. IAS because they can work
together.
> My company is very small and can't out-market any of the major players.
Nope, me neither - just wanting to try and scope out where exactly JINI fits
in the JNDI equation. As I (and probably many on this list) am not a JINI
expert. Most of what I was saying is not exclusively specific to IAS either.
> It sounds to me that Jini/JavaSpaces can also be used as pluggable backing
store
> with IAS.
sounds ok
> Sounds potent. I would still recommend SNDS as a cross-container solution.
Which EJB Servers does SNDS support/been tested with?
regards,
-Rob
----- Original Message -----
From: Freeman Jackson <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 19, 2000 1:55 PM
Subject: Re: replicated name services?
> Rob Castaneda wrote:
>
> > Hi Freeman,0
> >
> > Ok in IAS, fault-tolerance is done on the object reference.
> >
> > Clustering/Fault tolerance.
> >
> > For example I place the home object "CustomerHome" inside the /refs
context
> > of JNDI. In Inprise IAS, I can place many references of the same name,
> > under the same name. So I may have /refs/CustomerHome that points to
machine
> > X, and another /refs/CustomerHome that points to machine Y. The naming
> > service will dish out the references in, for example, a Round Robin
fashion.
> >
>
> Is this still a Stringification-based approach?
>
> I really don't want to make this a Jini vs. IAS because they can work
together.
> My company is very small and can't out-market any of the major players.
>
> >
> > Replication
> >
> > I can then configure this naming service to be a master, or a slave
(backup)
> > and to persist its memory in a "pluggable" backing store - which can be
a
> > replicated database.
> >
>
> It sounds to me that Jini/JavaSpaces can also be used as pluggable backing
store
> with IAS.
>
> >
> > So from the clients perspective it doesnt know, care, see etc. Which
JNDI
> > service it talks to. It just sets the JNDI properties to the Inprise
Context
> > factory etc. and then underneath it will bootstrap to the naming service
and
> > grab the reference from JNDI (not knowing which JNDI service it got it
from)
> >
> > So now the Naming Service itself is fault-tolerant and persisted, and
the
> > references inside it can be fault tolerant and clustered.This naming
> > service, and the above explained Clustering/Fault tolerance is also
given to
> > CORBA citizens.
> >
> > hope this helps,
>
> Sounds potent. I would still recommend SNDS as a cross-container solution.
>
>
>
> Freeman Jackson
> EJB Portal Management with Jini Connection Technology
> Siliware, Inc.
> Jini-JNDI Implementation: http://www.siliware.com/jinijndi.zip
> Draft: http://www.siliware.com/whatisnds.htm
> Draft: http://www.siliware.com/techsnds.htm
> Home Page: http://www.siliware.com
> Voice 201-239-0253
>
>
===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
