Project

General

Profile

Bug #3152

Use EcoGridServicesController with EcoGridWriter actor

Added by ben leinfelder almost 11 years ago. Updated over 9 years ago.

Status:
New
Priority:
Normal
Category:
data access
Target version:
Start date:
02/19/2008
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
3152

Description

I'm of two minds here:
Pro: It seems like having to enter both a PutService endpoint and an AuthenticationService endpoint as well as hardcoding your LDAP dn and password is a nuisance. It might be really neat if we used what just got built into the EcoGridServicesController to handle all the authentication stuff. We'd keep the put servuce endpoint (that's how we know how to authenticate), but all the other parameters would be made obsolete (AuthenticationManager would handle the login part).
Con: Requires that we have the destination Ecogrid node entered in our registry. The way it is now, I am free to put files to any ecogrid deployment (even my local development machine).

I'm not sure who might use this or how it would be most useful. Thoughts?

History

#1 Updated by Jing Tao almost 11 years ago

This actor is a rough test one which is in early stage. It needs to be polished. If we can use EcoGridServicesController to handle all the authentication stuff, that will be great.

#2 Updated by ben leinfelder over 10 years ago

retargeting for after 1.0 - not a high priority.

#3 Updated by Redmine Admin over 5 years ago

Original Bugzilla ID was 3152

Also available in: Atom PDF