[Go-essp-tech] node manager source

[Cinquini, Luca (3880)]

Hi Stephen,
	I remember Gavin mentioning the need to decouple the notification part of the node manager into a separate ESGF module - is that what you have in mind when you talk about building on that code ? I think it would be a great thing to do, so the node manager and the notification system can evolve independently.
thanks, Luca

On Jun 28, 2011, at 4:15 AM, <stephen.pascoe at stfc.ac.uk> <stephen.pascoe at stfc.ac.uk> wrote:

> You are not a pain Phil, you are the true voice of our requirements :-).  Not the only voice of course but it's good to have people telling us what features they want.
> 
> S.
> 
> ---
> Stephen Pascoe  +44 (0)1235 445980
> Centre of Environmental Data Archival
> STFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK
> 
> 
> -----Original Message-----
> From: Bentley, Philip [mailto:philip.bentley at metoffice.gov.uk] 
> Sent: 28 June 2011 11:12
> To: Pascoe, Stephen (STFC,RAL,RALSP)
> Cc: go-essp-tech at ucar.edu
> Subject: RE: [Go-essp-tech] node manager source
> 
> Hi, 
> 
>> Re. Nathan's reminder below.  This request is now really 
>> quite urgent.  We are getting requests from MOHC to get 
>> notification of some sort working -- maybe quite different to 
>> what was designed and implemented into the node manager.  So 
>> I need to spec-out requirements that allow MOHC users to work 
>> out what is being published, superseded, etc.
> 
> Presumably other modelling centres and end-user groups are pushing to
> see such functionality, right?
> 
> I'd hate to think that MOHC is alone in being a proverbial pain in the
> a** :-) :-)
> 
> Cheers
> Phil
> -- 
> Scanned by iCritical.
> _______________________________________________
> GO-ESSP-TECH mailing list
> GO-ESSP-TECH at ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/go-essp-tech