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.

Sign up for GitHub

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

Jump to bottom

v0.7.1 not compatible with v0.6.42 on signatureId #41

Open
codisan opened this issue May 2, 2017 · 1 comment
Open

v0.7.1 not compatible with v0.6.42 on signatureId #41

codisan opened this issue May 2, 2017 · 1 comment

Comments

@codisan
Copy link

codisan commented May 2, 2017

v0.6.42 Protocol generator:
Protocol.signatureId = '_r';

v0.7.1 Protocol generator:
Protocol.signatureId = 's';
@alaa-eddine
Copy link
Contributor

Hi @codisan ,
some protocole parameters was causing issues with a transport layer, so I modified it and made it configurable since v 0.7.0.

what you reported can only cause issues if you are using different versions of eureca.io in the client and server side, and this is not recommended, you should always use the same version in both sides.

if for some reason you want to configure your own protocole, you just need to make sure to set the same protocole in the client and server sides.

the protocoles fields are those defined here https://github.com/Ezelia/eureca.io/blob/master/src/Protocol.config.ts

in the server side

var Eureca = require('eureca.io');
//configure the protocole before anything else
Eureca.Protocol.signatureId = '_r';

in the client side

<head>
    <!-- init eureca.io -->
    <script src="/eureca.js"></script>
</head>
<body>
    <script>
Eureca.Protocol.signatureId = '_r';
    
     . . .
   </script>
</body>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alaa-eddine @codisan