Skip to content

Conversation

@a-canary
Copy link
Collaborator

@a-canary a-canary commented Jan 2, 2020

Refactoring H1 code to use destructors on transactions.

@a-canary a-canary self-assigned this Jan 2, 2020
@a-canary
Copy link
Collaborator Author

a-canary commented Jan 3, 2020

[approve ci autest]

ssn_id = _proxy_ssn->get_id();

if (_proxy_ssn->get_netvc()->get_context() == NET_VCONNECTION_IN) {
HTTP2_DECREMENT_THREAD_DYN_STAT(HTTP2_STAT_CURRENT_CLIENT_STREAM_COUNT, _thread);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use of destructors sounds great.

This is just an input for following changes. It would be great if we could generalize the destruction process, and put the code into ProxyTransaction's destructor and the details like this line into subclasses. This is the reason I was talking about decrement_txn_stat on a previous PR.

@maskit
Copy link
Member

maskit commented Jan 6, 2020

I'm not sure if this is really possible, but if we are going to delete transaction object this way (self destroy), it may be better to make the destructors private (or protected) members.

-SsnTrace & TxnTrace output for destructor debbuging
@a-canary
Copy link
Collaborator Author

a-canary commented Jan 8, 2020

[approve ci autest]

1 similar comment
@randall
Copy link
Contributor

randall commented Apr 17, 2020

[approve ci autest]

@a-canary
Copy link
Collaborator Author

a-canary commented May 1, 2020

this has been moved to h1outbound feature branch

@a-canary a-canary closed this May 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants