GWT Emite , any experience? - gwt

I am currentlty learning gwt emite for xmpp server communication using the GWT
Should I go ahead with this or any other GWT framework exists ?
Please help.

A google search reveals a couple of libraries
GWT Bindings for the Strophe XMPP library. This project intends to provide GWT bindings to the Strophe.js XMPP library
Atmosphere-GWT project. Although not exactly a general purpose XMPP library, Atmosphere appears to have some kind of support for XMPP.

Related

How to implement XMPP communication in Nativescript?

Is there any limitation in using a library like stanza.io for communication with an XMPP server like MongooseIM in Nativescript? What other alternatives are there?
If stanza.io supports NativeScript then there should not be any limitations.
On their GitHub main pager they say it's a Modern XMPP in the browser, with a JSON API. So it's mainly for browser env and I'm not sure about NativeScript.
As an alternative way - there is a xmpp.js lib which supports NativeScript. Their doc is a little bit shitty, but using src code there is a way to integrate successfully it.
There is a guide on how to use it for ReactNative, but you can some part from it for NativeScript, especially these part that are connected to the lib itself.
https://medium.com/#connectycube/xmpp-real-time-chat-in-react-native-8d6d5d23dd47
Also you can use some ready XMPP high level platforms for Chat, e.g. https://connectycube.com/2018/12/11/connectycube-textchat-code-sample-for-nativescript/
In this case you do not need to carte about XMPP server installation and monitoring
You will have to find a third party server or host your own one that implements XMPP protocols and connect to same using Websockets or XMPP plugin from your {N} application.
FYI, This XMPP plugin implements the same pod library explained in the MongooseIM docs, but the JavaScript apis are not fully implemented so you might have to access the native apis directly as needed.
You may also refer nativescript-xmpp-client, another exampel for XMPP implementation.

Update dynamic content in Browser plugin

I have a requirement to create a browser plugin. It should be a cross-browser plugin. The look and feel is similar to, say, Ask toolbar. My browser plugin should be able to make calls (using Cisco call control). Internally we will handle that no issue in that. But what is required is that previously we developed website for handling calls, which used java applets to dynamically change the status {Example when there is an incoming call Answer button would get enabled}. Will I be able to achieve it in Browser plugin.
Can I be able to use browser plugin over applet?
Is there any replacement for Java applet in the browser plugin?
Please help me in making a dynamic browser plugin.
Update:
I am planning to go for Kango cross-browser extension Framework. I need to know if Kango or any other extension framework support a socket communication where it can listern for sever update.
Thanks.
Can I use WebSocket (supported in HTML5) in the browser Extension? I learned that WebSocket method could not communicate directly with ordinary server and it need some changes in the server as well.
Ref: Connect to standard socket using WebSocket
Is there any other way other than WebSocket ?
Is there any open source available for javascript library which uses flash player?
If it could be opensource it could be helpful.
Cross browser plugin can be developed using some extension development tools such as Cross Rider or kango . I feel that Cross rider provides good support.
If we are going for Java applet for socket communication, definitely we are ready to face some trouble. Better avoid Java applet.
Socket communication can be achieved in the Web browser using many ways. "Web Socket" is one of them. The only constrain in using it is that it is supported only in HTML5 supporting browser or browser version. IE give support to WebSocket from IE11 only.
Another way to go is using Socket.io . It is having a good way of achieving it by using the available techniques in the client browser. For Example, if the client browser do not have a Flash player (Flash supports socket communication), it uses WebSocket or it "fallback" to available technique supported in browser.
Even node.js is a light weight technique.
The challenge here is we could not communicate with server which support socket with a "websocket" client. We need a proxy, Ref: Connect to standard socket using WebSocket
Hope this should help who need some start on Web Socket communication. If anyone want to add to this I would be very happy.

GWT RequestFactory and Server Push?

1- I have already used the following frameworks (Event based client-server) on GWT projects, and works fine with RPC call architecture.
GWT-Comet
GwtEventService
After searching, i found a lot of frameworks that treat the client server messaging exchange problem:
2- Jboss Errai framework
Great messaging service but i've not used it. I searched for only errai bus usage with gwt but nothing founded.
3- Atmosphere Framework
Seem to do same thing like comet but i've not used it.
http://async-io.org/tutorial.html
4- WebSocket
5- Spring-Integration-Cometd
6- Spring WebSocket
NOW :
I want to develop a project with Spring roo and GWT.
As Spring roo gwt based on RequestFactory architecture.
I think that we can use Comet or gwteventservice with RequestFactory architecture, but we need AutoBean to generate client side Entity interface on server side.
My question concern GWT RequestFactory :
How to integrate one of the frameworks above in gwt projects based on RequestFactory architecture? Is there any example ?!
Thanks

searching for a working GWT RPC library

im searching for a GWT-RPC lib for the client side to communicate with a zend framework php server
thus rpc like json, xml or rest would be interesting
all i find are projects which have been stuck in years 2007/08 which dont seem to work anymore
so is there anyone who can suggest a working library?
thx
As far as I know nobody has built a GWT-RPC to communicate with a non-Java server, to allow you to have the automatic object sharing between client (written in Java) and server (written in non-Java) that GWT-RPC provides.
Luckily, GWT provides a mechanism for communicating with a server in regular JSON, using RequestBuilder. See this link for more information about making regular HTTP requests in GWT.

differences between smack, tinder and whack

Can anyone tell me what the differences are between smack, tinder and whack?
Are tinder and whack slim-down versions of smack? Do the 3 libraries serve different purposes?
Smack is a client library. You can use it to log into an XMPP domain and make use of the functionality it provides. Typically, Smack is used to implement a instant messaging client.
Tinder is a low-level XMPP library. It provides Java implementations of basic XMPP entities, such as Stanzas (called 'Packet' in XMPP), JIDs and Components (which typically implement part of the functionality of an XMPP server). Although in theory, Tinder could be used to implement client functionality, it currently is primarily used on the server-side. Both Whack and Openfire (an XMPP server implementation) use Tinder-defined entities. Smack does not use Tinder at all.
Whack is Java library that is used to implement external components. Whack allows a Component (as defined in Tinder) to run as a stand-alone process. Whack allows you to connect this process to an XMPP domain. This way, you can extend the functionality provided by that domain without modifying the implementation of the server software.
I suggest reading this Blog entry
Introducing Tinder, an XMPP object implementation library
Smack -> Cross-platform real-time collaboration client optimized for business and organizations
Whack -> Java XMPP component library
Tinder -> Java based XMPP library, providing an implementation for XMPP stanzas and components
Tinder builds on code from Openfire and Whack. Does not replace Smack but will most likley replace Whack, OpenFire (formerly WildFire)
If you wanna create an application:
Smack will be client side Library
Whack and/or Tinder will be Server side Library