an xhrtransport can support both the `` xhr_streaming '' and `` xhr `` sockjs server transports . from a client perspective there is no implementation difference . typically an xhrtransport is used as `` xhr streaming '' first andthen , if that fails , as `` xhr '' . in some cases however it may be helpful to suppress xhr streaming so that only xhr is attempted . by default this property is set to false which means both `` xhr streaming '' and `` xhr '' apply . concode_field_sep Log logger concode_elem_sep boolean xhrStreamingDisabled concode_elem_sep HttpHeaders requestHeaders concode_elem_sep String PRELUDE concode_field_sep List<TransportType> getTransportTypes concode_elem_sep HttpHeaders getRequestHeaders concode_elem_sep ResponseEntity<String> executeInfoRequestInternal concode_elem_sep void connectInternal concode_elem_sep ResponseEntity<String> executeSendRequestInternal concode_elem_sep String executeInfoRequest concode_elem_sep boolean isXhrStreamingDisabled concode_elem_sep void executeSendRequest concode_elem_sep void setRequestHeaders concode_elem_sep String toString concode_elem_sep ListenableFuture<WebSocketSession> connect
void function ( boolean arg0 ) { this . xhrStreamingDisabled = arg0 ; }