issues
Data license: AGPL · Data source: ACEmulator Project
1 row where assignee = 3317737
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date), closed_at (date)
id ▼ | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
435988213 | MDExOlB1bGxSZXF1ZXN0MjcyNTc1NDkz | 1785 | network layer reduction | fartwhif 3317737 | closed | 0 | fartwhif 3317737 | 4 | 2019-04-23T04:01:32Z | 2019-04-23T23:11:35Z | 2019-04-23T23:11:35Z | COLLABORATOR | 0 | ACEmulator/ACE/pulls/1785 | - [x] Combine as many classes as possible without violating KISS or "the pattern" - [x] Implement I/O queues - [ ] Test mass connections and correct shortcomings of the implementation during extreme conditions - [ ] To prevent flooding, Implement inbound session packet governor and find threshold - proportionate to number of sessions? - [ ] To prevent flooding, Implement `ProcessFragment` governor and find threshold - proportionate to number of sessions? - [ ] `ProcessFragment` needs to be a producer for game loop consumer, game loop consumer pull X number of messages to keep server loop tight (500? 1000? more?) - [ ] S2C Retransmission request fulfillment, or C2S NAK, needs to have complexity added - if the packet being retransmitted contains physics data, that physics data needs to be replaced with the latest version sent if the latest version is not the one in the original packet. - [ ] Outbound queue needs an independent consumer thread, there should be no reason to send via game loop in bursts every game iteration, outbound can be constant - process outbound messages to players - add messages to outbound packets until 484 size reached or every 66ms - continue creating packets until outbound cleared - Outbound fragment bundling needs to be reduced to a single collection, as it adds unnecessary complexity at the cost of readability, understandability, and changeability without actually adding any benefit or working towards a required specification or towards an architectural norm. Since outbound queue will be sent by the fluidity of the independent consumer thread combined with the capabilities of the average modern internet connection fragment prioritization by queue or any other need for grouping them together is probably not needed, but I could be mistaken. Comments about this are most welcome. - [ ] Sessions should only be created upon authentication success, reducing the abuse potential and increasing network layer fitness. - the cookie in the cookie ex… | {"url": "https://api.github.com/repos/ACEmulator/ACE/issues/1785/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | ACE 79078680 | pull |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issues] ( [id] INTEGER PRIMARY KEY, [node_id] TEXT, [number] INTEGER, [title] TEXT, [user] INTEGER REFERENCES [users]([id]), [state] TEXT, [locked] INTEGER, [assignee] INTEGER REFERENCES [users]([id]), [milestone] INTEGER REFERENCES [milestones]([id]), [comments] INTEGER, [created_at] TEXT, [updated_at] TEXT, [closed_at] TEXT, [author_association] TEXT, [active_lock_reason] TEXT, [draft] INTEGER, [pull_request] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [state_reason] TEXT, [repo] INTEGER REFERENCES [repos]([id]), [type] TEXT ); CREATE INDEX [idx_issues_repo] ON [issues] ([repo]); CREATE INDEX [idx_issues_milestone] ON [issues] ([milestone]); CREATE INDEX [idx_issues_assignee] ON [issues] ([assignee]); CREATE INDEX [idx_issues_user] ON [issues] ([user]);