NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
> so we need some hooks into HttpClient. If you have any concrete API ideas, > send them over. I was thinking that there could be an optional argument to NetcdfDataset.acquire() and its friends, allowing the client to specify the HttpClient object to use. Or maybe the Credentials object. Or maybe even a username/password, although this wouldn't help for client-authenticated SSL. Jon 2009/1/20 John Caron <caron@xxxxxxxxxxxxxxxx>: > > > Jon Blower wrote: >>> so the remote site issues a challenge. do you just pass it on to your user >>> at her web page, or have you cached her credentials? >> >> Currently I imagine that the credentials (which may be a Grid proxy >> certificate, boo hiss) will be cached on the server. I was thinking >> that the user would log on to my web app, thereby creating a session >> object in which we can cache credentials. > > > so we need some hooks into HttpClient. If you have any concrete API ideas, > send them over. > -- Dr Jon Blower Technical Director, Reading e-Science Centre Environmental Systems Science Centre University of Reading Harry Pitt Building, 3 Earley Gate Reading RG6 6AL. UK Tel: +44 (0)118 378 5213 Fax: +44 (0)118 378 6413 j.d.blower@xxxxxxxxxxxxx http://www.nerc-essc.ac.uk/People/Staff/Blower_J.htm
netcdf-java archives: