{"action":"created","issue":{"url":"https://api.github.com/repos/acplt/open62541/issues/279","labels_url":"https://api.github.com/repos/acplt/open62541/issues/279/labels{/name}","comments_url":"https://api.github.com/repos/acplt/open62541/issues/279/comments","events_url":"https://api.github.com/repos/acplt/open62541/issues/279/events","html_url":"https://github.com/acplt/open62541/issues/279","id":88347016,"number":279,"title":"requirements and call logic for the client","user":{"login":"HolgerJeromin","id":2410353,"avatar_url":"https://avatars.githubusercontent.com/u/2410353?v=3","gravatar_id":"","url":"https://api.github.com/users/HolgerJeromin","html_url":"https://github.com/HolgerJeromin","followers_url":"https://api.github.com/users/HolgerJeromin/followers","following_url":"https://api.github.com/users/HolgerJeromin/following{/other_user}","gists_url":"https://api.github.com/users/HolgerJeromin/gists{/gist_id}","starred_url":"https://api.github.com/users/HolgerJeromin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/HolgerJeromin/subscriptions","organizations_url":"https://api.github.com/users/HolgerJeromin/orgs","repos_url":"https://api.github.com/users/HolgerJeromin/repos","events_url":"https://api.github.com/users/HolgerJeromin/events{/privacy}","received_events_url":"https://api.github.com/users/HolgerJeromin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-06-15T07:37:52Z","updated_at":"2015-06-15T08:31:27Z","closed_at":null,"body":"Right now the client code and example is synchronous and does not take care of the session keep alive by itself (if it has no work to do).\r\n\r\nI want to change this. My Idea was to reuse the pattern of the server code. \r\n\r\nBut perhaps it is better to decide what are our requirements for the client code before.\r\n\r\n* like now: synchronous fetching of one data from a server (and closing the connection).\r\n* fetching data from a server and leave (and keeping) the connection+session open for a long time.\r\n\r\nIMO the call logic should be the same as the server code. \r\nFor integration into ACPLT/OV it would be best to have a client_run_mainloop which also has different code for support of pthreads or cyclic call of client_run_mainloop().\r\n\r\nDo you have more wishes for the client integration into an application?\r\n"},"comment":{"url":"https://api.github.com/repos/acplt/open62541/issues/comments/111976785","html_url":"https://github.com/acplt/open62541/issues/279#issuecomment-111976785","issue_url":"https://api.github.com/repos/acplt/open62541/issues/279","id":111976785,"user":{"login":"jpfr","id":1726411,"avatar_url":"https://avatars.githubusercontent.com/u/1726411?v=3","gravatar_id":"","url":"https://api.github.com/users/jpfr","html_url":"https://github.com/jpfr","followers_url":"https://api.github.com/users/jpfr/followers","following_url":"https://api.github.com/users/jpfr/following{/other_user}","gists_url":"https://api.github.com/users/jpfr/gists{/gist_id}","starred_url":"https://api.github.com/users/jpfr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jpfr/subscriptions","organizations_url":"https://api.github.com/users/jpfr/orgs","repos_url":"https://api.github.com/users/jpfr/repos","events_url":"https://api.github.com/users/jpfr/events{/privacy}","received_events_url":"https://api.github.com/users/jpfr/received_events","type":"User","site_admin":false},"created_at":"2015-06-15T08:31:27Z","updated_at":"2015-06-15T08:31:27Z","body":"Good idea.\r\nWe need this also for subscriptions in the client.\r\n\r\nWe can move `src/server/ua_server_worker.c` to `/src/ua_async_events.c`.\r\nThen, the server and client can instantiate their very own mainloop."}}