Github user cloverhearts commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/921
@Leemoonsoo Thank you for the good opinion and Thank you for pointing out
an important point.
There are two reasons. First of all, I communication for the job manager
is, I think I would go more of many in the future further, than maybe notebook
message. Therefore, I felt the need to separate the part that processes the
message. This is expected to reduce confusion in the development of the future.
Second, duplicate code, I think also that it is a problem. However, when you
use a class named notebook socket for job communication in jobmanager,
misleading, it was thought to be able to misleading developers. I can integrate
it again, it is being modified to remove the duplicate.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
