dotgnu-general
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [DotGNU]GNU.RDF update 29-3-2003


From: Chris Smith
Subject: Re: [DotGNU]GNU.RDF update 29-3-2003
Date: Wed, 2 Apr 2003 12:50:42 +0100
User-agent: KMail/1.4.3

On Tuesday 01 Apr 2003 09:29, Peter Minten wrote:

> Good idea. Would the plugin system make it do the VRS thing?
>
> Now here's a cool idea: run the server as a DGEE plugin and the agents as
> local webservices (note that that does not mean the agents have to be
> programmed in C#). The agents could communicate with the DGEE through
> GNU.RDF API, an advantage of this system would be a good integration of the
> agents with the rest of DotGNU.

I think that is what I was getting at.  I hadn't necessarily considered that 
you'd write the 'agents' as webservices that run in one of the VMs.  The DGEE 
itself has (or will have soon) _internal_ webservices used for administrative 
purposes, these internal webservices are actually part of the DGEE 
infrastructure and are written in C (99% probability).

You could write a DGEE module or two that makeup your discovery server.  
They're just like the ServiceManager or ResourceManager of the DGEE.  They 
have a role to perform and called when requred - like when a request comes in 
for a 'Discovery Webservice', it is routed to your DGEE component instead of 
the VM pool.

This next bit assumes that when you call the DGEE 'discovery' webservices it 
searches its LOCAL copy of the worlds available 'stuff'... This assumption 
may be wrong, so read the following appropriately pls. :o)

Creating the collection of data that your discovery server searches against 
and serves to requestors needs to be done seperatly, by some automatic 
process or other.  This _can_ be integrated into the DGEE too but it is 
extrememly important that you consider these to aspects to data capture 
*seperatly* if you want to do any of the above.

Data capture and searching must be just that.  Two independant steps: 
1. discover whats out there and store that information.
2. Search against the stored information.

.... if however, the called DGEE discovery service is supposed to go off and 
search the web for stuff, then that's a different matter all together - and I 
don't know how (regardless of the DGEE) that would be achieved successfully 
and in a timely fashion anyway.


Interesting discussion.
Chris

-- 
Chris Smith
  Technical Architect - netFluid Technology Ltd.
  "Internet Technologies, Distributed Systems and Tuxedo Consultancy"
  E: address@hidden  W: http://www.nfluid.co.uk


reply via email to

[Prev in Thread] Current Thread [Next in Thread]