Thanks, Supun. This seems like a good think for the GSOC students to try out.
Marlon From: Supun Nakandala <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Monday, May 11, 2015 at 12:17 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Enabling Airavata Client and WSIS code as Service Providers in laravel PGA Hi All, I have done some changes to the structure of the PGA code base. Basically I have wrapped Airavata code and WSIS code as service providers. Now any Airavata API method or IS method can be directly used by calling WSIS:: or Airavata:: in any part of the application context. Laravel framework takes care of things like class loading and instantiate objects. I also considered wrapping these as packages and publishing them separately. But if we want to publish them they have to be first class repositories by them self and also this end up generating several configuration files for each package which is problematic. Furthermore to unify the property files I have added a php file named pga_config.php in the app/config directory. I have put all the IS configurations and only some of Airavata configurations to the file because I am not sure what these other properties mean in the application context. Any property value can be read any where in the application by simply calling Config::get('pga_config.airavata')['airavata-timeout'] etc. By following this way we don't need to read the ini file here and there and it is the recommended way to store and retrieve configurations in laravel. After moving all configuration to pga_config.php we can remove ini files Thanks Supun
