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.

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

Prioritise WS for optimal transport #250

Merged
merged 1 commit into from Jul 23, 2016
Merged

Prioritise WS for optimal transport #250

merged 1 commit into from Jul 23, 2016

Conversation

denji
Copy link
Contributor

@denji denji commented Jul 19, 2016

In raising this pull request, I confirm the following (please check boxes):

  • I have read and understood the contributing guidelines?
  • I have checked that another pull request for this purpose does not exist.
  • I have considered, and confirmed that this submission will be valuable to others.
  • Do the PHPCI tests pass?
  • Does the StyleCI test pass?

Description of change

Without these changes, we will always be pulling even if there is implementation of websocket.

  • Access to /.well-known/ is allowed RFC5785 (Let's Encrypt).
     app.listener = io.connect($('meta[name="socket_url"]').attr('content'), {
        query: 'jwt=' + $('meta[name="jwt"]').attr('content'),
+        transports: ['websocket', 'polling']
     });

Access to `/.well-known/` is allowed RFC5785
@@ -39,7 +39,8 @@ toastr.options.extendedTimeOut = 7000;
app.project_id = app.project_id || null;

app.listener = io.connect($('meta[name="socket_url"]').attr('content'), {
query: 'jwt=' + $('meta[name="jwt"]').attr('content')
query: 'jwt=' + $('meta[name="jwt"]').attr('content'),
transports: ['websocket', 'polling']
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't that the default option?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@REBELinBLUE REBELinBLUE merged commit dd8291d into REBELinBLUE:master Jul 23, 2016
REBELinBLUE added a commit that referenced this pull request Jul 23, 2016
* master:
  Updated dependencies
  Priority WS for optimal transport browser (#250)
  Ignore suggestions when installing Composer deps (#252)
  Fix style issue
  Revert "[Snyk Alert] Fix for 2 vulnerable dependency paths" (#245)
  fix: package.json & .snyk to reduce vulnerabilities (#244)

Conflicts:
	composer.lock
	resources/assets/js/app.js
@REBELinBLUE REBELinBLUE changed the title [IMPROVEMENT] Priority WS for optimal transport browser Priority WS for optimal transport browser Aug 6, 2016
REBELinBLUE added a commit that referenced this pull request Aug 6, 2016
* master: (60 commits)
  Updated CHANGELOG
  Fixes #257 - Touch files when extracting to prevent warnings about timestamps
  Update README.md
  Added a note about a common error
  Updated ioredis
  Updated google2fa library
  Fixes #254
  Fixes #256 - Git tag names causing a fatal error if they are not valid version string
  Fixed gulpfile so that assets don't get removed before they are versioned
  Updated dependencies
  Updated dependencies
  Priority WS for optimal transport browser (#250)
  Ignore suggestions when installing Composer deps (#252)
  Fix style issue
  Revert "[Snyk Alert] Fix for 2 vulnerable dependency paths" (#245)
  fix: package.json & .snyk to reduce vulnerabilities (#244)
  Handling the timeout checking for an update on github, i.e. when I am at work behind a proxy
  Added a check to the updatre script to ensure npm install has been run
  Update dialog.blade.php (#239)
  Silence PHPMD
  ...
@REBELinBLUE REBELinBLUE changed the title Priority WS for optimal transport browser Prioritise WS for optimal transport browser Aug 6, 2016
@REBELinBLUE REBELinBLUE changed the title Prioritise WS for optimal transport browser Prioritise WS for optimal transport Aug 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants