crypt32(2/3): Keep track of state in each message type's update function rather than in CryptMsgUpdate

Juan Lang juan.lang at gmail.com
Tue Mar 25 13:46:08 CDT 2008

Previous message: crypt32(1/3): Test updates after the final update to a detached message
Next message: crypt32(3/3): Allow one update to a decode message after the final update if it's a detached message
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

--Juan
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 0004-Keep-track-of-state-in-each-message-type-s-update-function-rather-than-in.txt
Url: http://www.winehq.org/pipermail/wine-patches/attachments/20080325/c30bc674/attachment.txt

Previous message: crypt32(1/3): Test updates after the final update to a detached message
Next message: crypt32(3/3): Allow one update to a decode message after the final update if it's a detached message
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the wine-patches mailing list