Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add SetThreadExecutionState to Kernel32 #720

Closed
Avalancs opened this issue Oct 29, 2016 · 0 comments
Closed

Add SetThreadExecutionState to Kernel32 #720

Avalancs opened this issue Oct 29, 2016 · 0 comments
Labels
feature request

Comments

@Avalancs
Copy link

I would like to request the addition of the function SetThreadExecutionState from Kernel32.dll to the winapi in JNA.

https://msdn.microsoft.com/en-us/library/windows/desktop/aa373208(v=vs.85).aspx
This function makes it very easy to prevent windows from going to sleep/hibernation while for example a download is going on in the target application.
@Avalancs Avalancs mentioned this issue Oct 29, 2016
Open
matthiasblaesing added a commit to matthiasblaesing/jna that referenced this issue Nov 15, 2016
@matthiasblaesing
Implement SetThreadExecutionState
df0eb93 
Closes: java-native-access#720
@matthiasblaesing matthiasblaesing mentioned this issue Nov 15, 2016
Merged
mstyura pushed a commit to mstyura/jna that referenced this issue Sep 9, 2024
@normanmaurer
Only create a new QuicChannel when receiving an INITIAL packet (java-…
4fc6297 
…native-access#720)

Motivation:

We should only try to create a new QuicChannel when receiving an INITIAL
packets. For all the other packets we want to just drop the packet on
the floor if there is no existing mapping.

Modifications:

Only create a new QuicChannel on receiving an INITAL packet

Result:

Correctly handle creation of new QuicChannel
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@matthiasblaesing @Avalancs