Documentation for chat is a mess

The documentation of the chat plugin is more than inadequate!

I have now bought the extention extra and have had it for several years and I still don’t know which json requests and responses come to and from the server and how they are processed in the chat… Can you please point me to some decent documentation in so I can integrate my own server with my own database into the plugin?

I need this information as soon as possible.

Thanks
Michael

Greetings @Michael!

We have a description of all requests, and in the same article there is a mention that the chat works on websockets: Working with Server of UI Complex Widgets, Chat Webix Docs

We always update documentation based on user requests, so could you give us more detailed feedback? Is the information in the article insufficient or irrelevant? We will be extremely grateful to you for as detailed feedback as possible, it will help us make the documentation better for our users. Thank you in advance!

Thank you very much for your response and info.
Sorry, but maybe I don’t understand how to handle over websockets to my central server. I don’t understand this:

webix.ui({
    view: "chat",
    url:"http://localhost:3200/"
});

the webix ui is on client side so I don’t have a localhost ! On my client side there isn’t no one listen to port 3200…
Also all my requests are secured and it could be that some defender and protection…
Like here Writing WebSocket servers - Web APIs | MDN

I use to have connect over ajax requests like in datatables How can I communicate my chat with my web-server?

Sorry, for my inexperience and ignorance. could you please give me a hint how to communicate with my web-server?

Thank you
Michael

I start running npm install in chat folder root and I got this:

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@xbs%2fwebix-pro - Not found
npm ERR! 404
npm ERR! 404  '@xbs/webix-pro@10.0.6' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'chat'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

I also get this

npm WARN deprecated rollup-plugin-terser@6.1.0: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated opn@6.0.0: The package has been renamed to `open`
npm WARN deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated fsevents@1.2.13: The v1 package contains DANGEROUS / INSECURE binaries. Upgrade to safe fsevents v2
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated


We apologize for the delayed response.

As for the 404 error, your license is valid, so you have access to the @xbs/webix-pro@10.0.6 package. Perhaps it is installed on you with the wrong registry. A working method for different versions of node/npm is described here: Webix Installation Guide of Getting Started, Start Coding with Webix Webix Docs.
The warnings that appear do not need attention. Since some dependencies are outdated, they work stably and will be updated in future versions.

Speaking of localhost on port 3200, this is just an example. In all examples, we write some kind of URL that roughly corresponds to what needs to be used with our demo backends.
Here, for example, is a chat background that can be used as a basis/reference for your chat:

Depending on how the backend is running (docker/standalone), the URL for the chat configuration will be http://localhost:3000 or http://localhost:8040.

As for the chat and web server connection, our component allows you to completely replace our backend layer with a custom one.

Our backend is quite secure.
It is assumed that the user first undergoes authorization (outside of our component), during which a temporary token is transferred to the client (this is a cryptographically signed consent by the server that the user can use the chat, his ID in the chat).
And then when the chat is connected, a token is transferred there

That is, authorization is carried out first, and the chat does not interact with the authorization topic.

It is impossible to fake the token; it is signed by the server.
To steal a token, you need to have access to the user’s session, which means you need to hack the site or his account, which is already a big problem.

Please, if you have any further questions, be sure to ask. We will be happy to answer!

Hello NatashaS.
I’m very thankful while you helping me to go further… I’ll check this out… and come back…
Have a nice weekend

Michael

1 Like

Hello NatashaS.

At the moment I’m working with cakephp on a ubuntu server with a mysql database. For the chat I don’t want to test it over nodejs or some something. I want to use this chat tool like all other tools over a asynchron or synchron request to or from the server. In my test environment I use vagrant. Also I don’t know how to handle this

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@xbs%2fjet-helpers - Not found
npm ERR! 404
npm ERR! 404  '@xbs/jet-helpers@1.1.2' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'chat1006'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:

At this moment I really need a help ticket for the first time!

Hope you can help me.

Michael