[kepler-dev] [Bug 3152] New: - Use EcoGridServicesController with EcoGridWriter actor

bugzilla-daemon@ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Tue Feb 19 10:57:07 PST 2008


           Summary: Use EcoGridServicesController with EcoGridWriter actor
           Product: Kepler
           Version: 1.0.0beta3
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: data access
        AssignedTo: leinfelder at nceas.ucsb.edu
        ReportedBy: leinfelder at nceas.ucsb.edu
         QAContact: kepler-dev at ecoinformatics.org

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?

More information about the Kepler-dev mailing list