{"action":"opened","issue":{"url":"https://api.github.com/repos/real-logic/Aeron/issues/56","labels_url":"https://api.github.com/repos/real-logic/Aeron/issues/56/labels{/name}","comments_url":"https://api.github.com/repos/real-logic/Aeron/issues/56/comments","events_url":"https://api.github.com/repos/real-logic/Aeron/issues/56/events","html_url":"https://github.com/real-logic/Aeron/issues/56","id":57591321,"number":56,"title":"Persistence/acks question","user":{"login":"philippsushkin","id":10991949,"avatar_url":"https://avatars.githubusercontent.com/u/10991949?v=3","gravatar_id":"","url":"https://api.github.com/users/philippsushkin","html_url":"https://github.com/philippsushkin","followers_url":"https://api.github.com/users/philippsushkin/followers","following_url":"https://api.github.com/users/philippsushkin/following{/other_user}","gists_url":"https://api.github.com/users/philippsushkin/gists{/gist_id}","starred_url":"https://api.github.com/users/philippsushkin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/philippsushkin/subscriptions","organizations_url":"https://api.github.com/users/philippsushkin/orgs","repos_url":"https://api.github.com/users/philippsushkin/repos","events_url":"https://api.github.com/users/philippsushkin/events{/privacy}","received_events_url":"https://api.github.com/users/philippsushkin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-02-13T12:04:32Z","updated_at":"2015-02-13T12:04:32Z","closed_at":null,"body":"I am trying to figure out how to implement following:\r\n\r\n1. infinite persistable retransmission buffer\r\n- multicast publisher without any limitation by receivers\r\n- receivers \"late join\" handled  somehow (with unicast retransmits like on naks or smthing custom)\r\n- persistent means that i can stop/start publisher application and continue publish where I was finished. I agree to pay some price for that, in general I see custom buffer/term management where they not rotated but asynchronously written to disk.\r\nAre there some extension points I can play with?\r\n \r\n2. handle/manage receiver cumulative acks after _message processing by app on subscriber side_ in consistent but more or less cheap way on publisher\r\n- use receiver status message?\r\n- separate channel for acks?\r\n\r\nCould you please advice if it is achievable/reasonable/applicable to Aeron at all.\r\nOr just point me direction/extension points where to dig.\r\n\r\nThanks in advance.\r\n"}}