Use EcoGridServicesController with EcoGridWriter actor
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?