Remove the need of lambdaws.start
EFF opened this issue · comments
@EFF agreed - seems redundant.
@EFF in reference to
exports.start = function (startedCallback) {
// TODO : move this in the function invocation ?
_sqsHelper.startQueue(startedCallback);
};
Which invocation are you referring to? _initializeAwsHelpers
? SQSHelper
? Or LambdaHelper
?
I see a few possibilities.
@GhostsNstuff I mean when the clouded function is invoked.
When you
var cloudedFunc = lambdaws.create(myfunc);
// and then
cloudedFunc(); // this is the function invocation to me
I haven't look for better solutions that's the thing that came to me, there might be better solutions.
You're welcome to assign yourself in the public trello board
@EFF gotcha, so from the user's perspective. I wasn't sure if you were referring to some internal optimization. I'll take a look again after work tonight.
@GhostsNstuff I wasn't super clear my bad ! Great, keep me posted on the gitter chat
@EFF no stress man - sounds good 👍
Fixed in #54