{"action":"created","issue":{"url":"https://api.github.com/repos/deepdream-community/opendream/issues/3","labels_url":"https://api.github.com/repos/deepdream-community/opendream/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/deepdream-community/opendream/issues/3/comments","events_url":"https://api.github.com/repos/deepdream-community/opendream/issues/3/events","html_url":"https://github.com/deepdream-community/opendream/issues/3","id":94429529,"number":3,"title":"web interface","user":{"login":"SlimeQ","id":3934698,"avatar_url":"https://avatars.githubusercontent.com/u/3934698?v=3","gravatar_id":"","url":"https://api.github.com/users/SlimeQ","html_url":"https://github.com/SlimeQ","followers_url":"https://api.github.com/users/SlimeQ/followers","following_url":"https://api.github.com/users/SlimeQ/following{/other_user}","gists_url":"https://api.github.com/users/SlimeQ/gists{/gist_id}","starred_url":"https://api.github.com/users/SlimeQ/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SlimeQ/subscriptions","organizations_url":"https://api.github.com/users/SlimeQ/orgs","repos_url":"https://api.github.com/users/SlimeQ/repos","events_url":"https://api.github.com/users/SlimeQ/events{/privacy}","received_events_url":"https://api.github.com/users/SlimeQ/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-07-11T03:13:44Z","updated_at":"2015-07-17T17:22:47Z","closed_at":"2015-07-17T17:22:47Z","body":"i want to have a web interface that can be used to send/receive images to the program, and also have a webcam. the logistics here can go a few ways. probably the most sensible way is to have a python web server which simply receives images and processes them. however, python is going to be quite busy between requests, so i think it makes the most sense to have it block at this time and then re-open the connection on completion and send the processed file back. of course this will make it impossible to remotely stop the process, which is unfortunate. i've been tossing around the idea of having a node.js server which is capable of handling requests asynchronously and starting/killing the process on command. it would also accept images from the python process via a socket as it ran, which it could then dump to database, email to tumblr, or push to a connected user. i think this is a good idea.\r\n\r\nsuggestions are welcome. i've noticed that clouddream has an interface already that has much of this functionality, so that is definitely worth looking into."},"comment":{"url":"https://api.github.com/repos/deepdream-community/opendream/issues/comments/122347458","html_url":"https://github.com/deepdream-community/opendream/issues/3#issuecomment-122347458","issue_url":"https://api.github.com/repos/deepdream-community/opendream/issues/3","id":122347458,"user":{"login":"SlimeQ","id":3934698,"avatar_url":"https://avatars.githubusercontent.com/u/3934698?v=3","gravatar_id":"","url":"https://api.github.com/users/SlimeQ","html_url":"https://github.com/SlimeQ","followers_url":"https://api.github.com/users/SlimeQ/followers","following_url":"https://api.github.com/users/SlimeQ/following{/other_user}","gists_url":"https://api.github.com/users/SlimeQ/gists{/gist_id}","starred_url":"https://api.github.com/users/SlimeQ/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SlimeQ/subscriptions","organizations_url":"https://api.github.com/users/SlimeQ/orgs","repos_url":"https://api.github.com/users/SlimeQ/repos","events_url":"https://api.github.com/users/SlimeQ/events{/privacy}","received_events_url":"https://api.github.com/users/SlimeQ/received_events","type":"User","site_admin":false},"created_at":"2015-07-17T17:22:47Z","updated_at":"2015-07-17T17:22:47Z","body":"I am closing this issue because it's more or less been done. [I've created a new issue with regards to packaging here.](https://github.com/deepdream-community/opendream/issues/4)"}}