Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TODO: Client/Server extension #3

Closed
vfilimonov opened this issue Jan 8, 2018 · 2 comments
Closed

TODO: Client/Server extension #3

vfilimonov opened this issue Jan 8, 2018 · 2 comments
Assignees

Comments

@vfilimonov
Copy link
Owner

Account for the case when powerpoint and ipython notebook are not running on the same machine (e.g. when notebook is hosted on the server/cloud).

Possible variant:

  • Running a server on Windows machine where powerpoint is used. Simple HTTP server is a good option to not mess up with sockets.
  • Client side (bypassing import win32com) to be run on the remote machine and will send command+png to the server instead of direct use of COM.
@vfilimonov vfilimonov self-assigned this Jan 8, 2018
@vfilimonov
Copy link
Owner Author

Client options:

Option A: direct connection to server and GET/POST via requests.

Option B: injection of javascript to IPython notebooks to be executed in browser.

@vfilimonov
Copy link
Owner Author

vfilimonov commented Jan 15, 2018

The chosen design of the client-server architecture has its reasons: If the local machine is not exposed to the remote, the only other option of communicating could be to start server on the remote side. However in this case either (i) a permanent connection between local client and server is needed or (ii) regular requests from local client to the server on existence of new actions to do with the powerpoint. Neither of the options looked good to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant