Tickets :: Comment on [#2782] S/MIME Sign using browser capabilities

Search Results: 27 of 574 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: . .. ,. ..__. . \| \| \./ \|__\|\| \| \| \|/\\| \| \| \|\|__\|\__\|
Comment	>> Without AJAX: > >> ~~~~~~~~~~~~~ > >> Brief: > >> ------ > >> 1) Submit the form as usual. > >> 2) Build a text/plain MIME for each recipient. > >> 3) Marshall return values as form hidden inputs. > >> 4) Render the compose page again. > >> 5) Hook on onload event to sign text/plain MIMES. > >> 6) ReSubmit this form. > >> 7) Unmarshall submitted form hidden inputs to carry on. > >> 8) Build a multipart/signed for each pair of (text/plain, signature) > >> 9) Now send all as usual. > > > > I gave it another look at this and I believe some of the > un/marshalling (i mean serializing) is unnecesary, just by changing > the way I suggested to chop the switch case. The variables for > buildAndSendMessage() are taken from the form submition. If I move up > case 'submit_mime' to the top, all the variables will be re taken. > > > > I am working to confirm this. Maybe the re-submition strategy isn't > that painful, although I think we could do it better with Ajax later.
Attachment
Watch this ticket