I guess I meant both : I don't think either requires security for discovery. Matt
--------------------------------------------------------- Please note my working days from 5/1/2009 are Mon, Wed, Thurs only. [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Lowe, D (Dominic) Sent: 21 May 2009 13:02 To: NERC DataGrid Technical List; NERC DataGrid Technical List; Pepler, SJ (Sam); Harwood, AS (Andrew); Lawrence, BN (Bryan); Donegan, SJ (Steve) Subject: RE: [ndg-technical] Standalone OGC client - connecttodiscovery/browse? Matt, are you talking about a CEDA public rollout of the discovery service -as opposed to a "development" roll out on neptune? Cheers Dom -----Original Message----- From: [email protected] on behalf of Pritchard, MJ (Matt) Sent: Thu 21/05/2009 12:01 To: NERC DataGrid Technical List; Pepler, SJ (Sam); Harwood, AS (Andrew); Lawrence, BN (Bryan); Donegan, SJ (Steve) Subject: RE: [ndg-technical] Standalone OGC client - connecttodiscovery/browse? > (I'm not sure browse/discovery actually needs securing; the other part of the MILK stack, the atom editor does, although this could just be ran as an internal, standalone app to get round this). In my understanding, browse/discovery does not need securing, and yes, we plan only to run the atom editor as an internal standalone app, so again no need. Anyone else please shout if you disagree. Andrew and Steve (between them) are probably best placed to look after the roll-out of browse app & discovery client/server : Andrew for the pylons / apache (i.e. client) side of things and Steve for Java / Tomcat ...but this obviously needs to be done together. Matt --------------------------------------------------------- Please note my working days from 5/1/2009 are Mon, Wed, Thurs only. [email protected] ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: 21 May 2009 09:24 To: NERC DataGrid Technical List Subject: Re: [ndg-technical] Standalone OGC client - connect todiscovery/browse? Hi Dom, The discovery/browse code, now part of the MILK stack, is pretty much ready to go. I've been tweaking things on the discovery client in the last week or so, but I think I've done everything I need to do. The remaining task is to sort out security and formalise a roll out to test/production. Security may not actually be a concern, but I'm waiting to hear back opinions from various parties (I'm not sure browse/discovery actually needs securing; the other part of the MILK stack, the atom editor does, although this could just be ran as an internal, standalone app to get round this). As for the roll out, I'm not sure where the responsibility for this lies as it's not something I've been formally tasked to do. I'm happy to do it, but it may be more useful for whoever is going to be looking after the service (I guess Andrew?), to do it. Regards, Calum. Tessella plc Bosinney Court, 124-126 Stockbridge Road, Winchester, SO22 6RN E: [email protected], T: +44 (0)1962 850055, F: +44 (0)1962 851122 www.tessella.com Registered in England No. 1466429 This message is commercial in confidence and may be privileged. It is intended for the addressee(s) only. Access to this message by anyone else is unauthorized and strictly prohibited. If you have received this message in error, please inform the sender immediately. Please note that messages sent or received by the Tessella e-mail system may be monitored and stored in an information retrieval system. Dominic Lowe <[email protected]> Sent by: [email protected] 20/05/2009 11:32 Please respond to NERC DataGrid Technical List <[email protected]> To "NERC DataGrid Technical List" <[email protected]> cc Subject [ndg-technical] Standalone OGC client - connect to discovery/browse? Hi All, especially Steve, Calum, but possibly others, I have made some progress in isolating the WMS client (visualisation code from old NDG pylons stack) and setting it up as a standalone WMS client on Neptune. I've also added a WCS download button so you can download the currently visualised data. The client is currently initiated in the url via Web Map Context URLs: http://ndg3beta.badc.rl.ac.uk/cowsclient/wmsviz?ENDPOINT=http://ndg3beta .badc.rl.ac.uk/cows/famous/wms?request=GetContext The next stage is to try and couple this client to discovery/browse - and initiated the client from links in Browse records (& the shopping cart). This is where I need help... What's the current status of discovery/browse? Is it deployed on Neptune now? Are we at a point were we can start coupling it to this visualisation client, presumably via WMC links in MOLES records? Cheers Dom p.s. there are still lots of bugs in the client but my preference is to work on hooking it up to browse now and fixing the bugs later. _______________________________________________ NDG-technical mailing list [email protected] http://lists.ncas.ac.uk/mailman/listinfo/ndg-technical -- Scanned by iCritical. -- Scanned by iCritical. -- Scanned by iCritical. _______________________________________________ NDG-technical mailing list [email protected] http://lists.ncas.ac.uk/mailman/listinfo/ndg-technical
