I've used Microsoft SignalR for real-time web messaging before. It has a
javascript client library but requires jQuery. It would be nice if there is
a qooxdoo equivalent though so we can throw away the jQuery requirement.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/WebSo
So what happened to this? Does it become a contrib ? where it gone ?
I didn't see websocket qooxdoo source and no contribs either.
I really believe qooxdoo need websocket functionality.
On Mon, Dec 29, 2014 at 8:21 PM, halcwb wrote:
> Phyo Arkar wrote
>> Check the development process of Atom.io a
Phyo Arkar wrote
> Check the development process of Atom.io and how lively and thriving it is
> , although it is Coffeescript.
> Also check rethinkdb's Github.
> If qooxdoo is easy to contribute and development process is open , it will
> grow a lot faster , and will have alot of users.
>
> Peopl
On Thu, 27 Nov 2014, Phyo Arkar wrote:
> Back on topic, Thanks a lot stefan , i really believe Websocket need to be
> inside Qooxdoo . As installing contributions in qooxdoo need a quite abit
> of work.
Well ... compared to the actual implementation this is probably a small
percentage of the eff
Check the development process of Atom.io and how lively and thriving it is
, although it is Coffeescript.
Also check rethinkdb's Github.
If qooxdoo is easy to contribute and development process is open , it will
grow a lot faster , and will have alot of users.
People can contribute at Atom.io and
I agree with Stefan; opening up the development process would be good for the
community and good for Qoxodoo.
John
> On 13 Nov 2014, at 08:27, d...@cost-savers.net wrote:
>
> Hi Fritz!
>
>> I also understand the argument about core functionality. But putting it
>> there only helps if 1&1 has
Hi Fritz!
> I also understand the argument about core functionality. But putting it
> there only helps if 1&1 has the necessary ressources to maintain it (or at
> least to make sure updates/fixes are checked and integrated in a timely
> manner).
It is so true and therefore maybe 1&1 should look f
Cool ... (although I don't have an immediate application for that, but I
know somebody with a Qooxdoo project using web sockets).
I also understand the argument about core functionality. But putting it
there only helps if 1&1 has the necessary ressources to maintain it (or at
least to make sure up
Hi Martin,
It is easy to keep it as a contribution if that is what you want.
We chose an enhancement bug as Script/Xhr/Jsonp communication are core
functionality and we believe websocket should be too.
We also used the qx.io namespace of the same reason.
We believed it might help you
...but
Hallo Stefan,
first of all, thank you very much. I didn’t have time to check out any details
but one questions came to my mind right away. Why did you decide to use a pull
request instead of a contribution? This topic seems to be so huge and self
contained, it could be easily a contribution as w
We have sent a pull request to the qooxdoo.
As WebSockets have not been implemented the qooxdoo way with basic, fallback,
reconnection, pool, cache, data binding etc, we decided to start it.
Any suggestions on it would be appreciated.
Stefan
11 matches
Mail list logo
