session-desktop/libtextsecure/protobufs.js

;(function() {

    function loadProtoBufs(filename) {
        return dcodeIO.ProtoBuf.loadProtoFile({root: 'protos', file: filename}).build('textsecure');
    };

    var pushMessages     = loadProtoBufs('IncomingPushMessageSignal.proto');
    var subProtocolMessages = loadProtoBufs('SubProtocol.proto');
    var deviceMessages   = loadProtoBufs('DeviceMessages.proto');

    window.textsecure = window.textsecure || {};
    window.textsecure.protobuf = {
        IncomingPushMessageSignal : pushMessages.IncomingPushMessageSignal,
        PushMessageContent        : pushMessages.PushMessageContent,
        ProvisioningUuid          : deviceMessages.ProvisioningUuid,
        ProvisionEnvelope         : deviceMessages.ProvisionEnvelope,
        ProvisionMessage          : deviceMessages.ProvisionMessage,
        DeviceControl             : deviceMessages.DeviceControl,
        WebSocketResponseMessage  : subProtocolMessages.WebSocketResponseMessage,
        WebSocketRequestMessage   : subProtocolMessages.WebSocketRequestMessage,
        WebSocketMessage          : subProtocolMessages.WebSocketMessage
    };
})();
Refactor textsecure.protos -> textsecure.protobuf DRY up protobuf declarations and move to a slightly briefer naming convention. Also dropped some ArrayBuffer -> string conversions as ProtoBuf.js handles ArrayBuffers just fine, and in fact, more efficiently than strings. Finally, dropped the btoa() wrappers, because that incurs an extra string -> string conversion before the protobuf's internal string -> array buffer conversion. In lieu of btoa, we can simply pass in the optional string encoding argument to the protobuf's decode method, which in these cases should be 'binary'. Related: #17 11 years ago			`;(function() {`

			`function loadProtoBufs(filename) {`
			`return dcodeIO.ProtoBuf.loadProtoFile({root: 'protos', file: filename}).build('textsecure');`
			`};`

			`var pushMessages = loadProtoBufs('IncomingPushMessageSignal.proto');`
New websocket protocol 11 years ago			`var subProtocolMessages = loadProtoBufs('SubProtocol.proto');`
Refactor textsecure.protos -> textsecure.protobuf DRY up protobuf declarations and move to a slightly briefer naming convention. Also dropped some ArrayBuffer -> string conversions as ProtoBuf.js handles ArrayBuffers just fine, and in fact, more efficiently than strings. Finally, dropped the btoa() wrappers, because that incurs an extra string -> string conversion before the protobuf's internal string -> array buffer conversion. In lieu of btoa, we can simply pass in the optional string encoding argument to the protobuf's decode method, which in these cases should be 'binary'. Related: #17 11 years ago			`var deviceMessages = loadProtoBufs('DeviceMessages.proto');`

			`window.textsecure = window.textsecure \|\| {};`
			`window.textsecure.protobuf = {`
			`IncomingPushMessageSignal : pushMessages.IncomingPushMessageSignal,`
			`PushMessageContent : pushMessages.PushMessageContent,`
Update to real server provisioning API 11 years ago			`ProvisioningUuid : deviceMessages.ProvisioningUuid,`
Mostly done device-bringup stuff 11 years ago			`ProvisionEnvelope : deviceMessages.ProvisionEnvelope,`
			`ProvisionMessage : deviceMessages.ProvisionMessage,`
New websocket protocol 11 years ago			`DeviceControl : deviceMessages.DeviceControl,`
			`WebSocketResponseMessage : subProtocolMessages.WebSocketResponseMessage,`
			`WebSocketRequestMessage : subProtocolMessages.WebSocketRequestMessage,`
			`WebSocketMessage : subProtocolMessages.WebSocketMessage`
Refactor textsecure.protos -> textsecure.protobuf DRY up protobuf declarations and move to a slightly briefer naming convention. Also dropped some ArrayBuffer -> string conversions as ProtoBuf.js handles ArrayBuffers just fine, and in fact, more efficiently than strings. Finally, dropped the btoa() wrappers, because that incurs an extra string -> string conversion before the protobuf's internal string -> array buffer conversion. In lieu of btoa, we can simply pass in the optional string encoding argument to the protobuf's decode method, which in these cases should be 'binary'. Related: #17 11 years ago			`};`
			`})();`