river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From m..@martinwills.com
Subject Re: Lookup Service Discovery using DNS?
Date Tue, 12 Jan 2010 13:19:40 GMT
Just out of curiosity, why wouldn't it be taken on as a project within
this group to do:
a) Create an enhanced specification for Reggie to allow it to act as a
global registry with sufficient permissions and scope.
b) Create a new service which sole purpose is to act as a global registry.

Either of these can be accomplished within the current River framework.


> On Jan 12, 2010, at 620AM, Sim IJskes - QCG wrote:
>> Dennis Reedy wrote:
>>> On Jan 12, 2010, at 557AM, Sim IJskes - QCG wrote:
>>>> Peter Firmstone wrote:
>>>>> Anyone got any opinions about Lookup Service Discovery?
>>>>> How could lookup service discovery be extended to encompass the
>>>>> internet?   Could we utilise DNS to return locations of Lookup
>>>>> Services?
>>>>> For world wide lookup services, our current lookup service might
>>>>> return a massive array with too many service matches. Queries present
>>>>> the opportunity to reduce the size of returned results, however
>>>>> security issues from code execution on the lookup service present
>>>>> problems.
>>>> I haven't seen any world wide deployments yet, at least not on my
>>>> bench. :-) And i would like to reserve my definite judgement before i
>>>> have had an actual production deployment of such a service.
>>>> As i understand it, reggie will replicate information between its
>>>> peers.
>>> Reggie does no such replication.
>> That makes it easier to create islands! :-)
>> I've had 2 reggies running, and the service was registered on both of
>> them (if i remember correctly), so this was the clients doing?
> Yep

View raw message