Open kuna opened 9 years ago
thank you!
I still can't understand what the 'Kill the job' is. After the job killed, a user can't send other command or should I make other driver after the job killed?
There's a bit of confusion here.
You can describe your assumptions in your README and design a system based on the assumptions, but I think the following makes more sense.
In this assignment, a job can be interpreted as a command requested by a user. So, after the job gets killed, a user can still send another command.
On Mon, Jun 8, 2015 at 7:29 PM, HurSungYeon notifications@github.com wrote:
I still can't understand what the 'Kill the job' is. After the job killed, a user can't send other command or should I make other driver after the job killed?
— Reply to this email directly or view it on GitHub https://github.com/swsnu/discussionswppspr2015/issues/25#issuecomment-109944401 .
Byung-Gon Chun
Sorry, I think my comment has created ambiguity on what it means to kill a job. As @bgchun said, please clarify your interpretation in your README so we don't misunderstand your intentions.
Now I understand well. Thanks for quick replying.
I have two questions.
kills the job
means kill job driver. am I correct?n is a configuration parameter
means that I need to passn
as argument likebindNamedParameter
(as far as there's no method to pass argument in ServiceConfiguration), or it means client(user) just configurable(like hard-coded one)?thank you.