Re: [qooxdoo-devel] Node.js and qooxdoo statics
Glad it worked for you! On Mon, Sep 17, 2012 at 7:03 AM, Florin Jurcovici wrote: >> I would throw your initializer in a constructor if pointing to a >> static. Define your props like this: > > I was suspecting something like this, but didn't dig deep enough into > properties. I did the changes you suggested (deferred initialization > of non-nullable properties), and now node loads the class. Thank you > very much. > > -- > Rule of Diversity: Distrust all claims for “one true way”. (Eric S. > Raymond, The Art Of Unix Programming) > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Node.js and qooxdoo statics
> I would throw your initializer in a constructor if pointing to a > static. Define your props like this: I was suspecting something like this, but didn't dig deep enough into properties. I did the changes you suggested (deferred initialization of non-nullable properties), and now node loads the class. Thank you very much. -- Rule of Diversity: Distrust all claims for “one true way”. (Eric S. Raymond, The Art Of Unix Programming) -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Node.js and qooxdoo statics
I would throw your initializer in a constructor if pointing to a
static. Define your props like this:
properties: {
someProp: {
nullable: false,
deferredInit: true,
check: [test.ClassWithStatics.constant1, test.ClassWithStatics.constant2]
}
}
And then inside of your constructor initialize someProp
construct: function () {
this.base(arguments);
this.initSomeProp(this.constructor.constant1);
}
Hope this helps!
On Mon, Sep 17, 2012 at 6:08 AM, franck34 wrote:
> I'm developing an app using appjs+nodejs+qooxdoo.
>
> The main problem is SCOPE.
>
> Hard to say what's your problem, but warning about binding and scope ...
>
> I'm using lot's of qx.lang.Function.bind and var self = this; in my code.
>
> Don't know exactly what's your problem but just take care of binding/scope.
>
>
> On Mon, Sep 17, 2012 at 2:42 PM, Florin Jurcovici
> wrote:
>>
>> I have something like:
>>
>> qx.Class.define("test.ClassWithStatics",
>> {
>> statics:
>> {
>> constant1: "john",
>> constant2: "doe"
>> },
>>
>> properties:
>> {
>> someProp:
>> {
>> init: test.ClassWithStatics.constant1,
>> check: [test.ClassWithStatics.constant1,
>> test.ClassWithStatics.constant2]
>> }
>> }
>> });
>>
>> in a class which I compile into a qooxdoo app, and it works fine.
>>
>> However, when I try to use the same class on node.js (after having
>> required qooxdoo), I get:
>>
>> TypeError: Cannot read property 'constant1' of undefined
>>
>> at line "init: test.ClassWithStatics.constant1," when requiring
>> ClassWithStatics.js.
>>
>> Does anybody have any idea why? Is there a nice workaround, i.e. one
>> that shouldn't force me to move the constants out of
>> test.ClassWithStatics?
>>
>> I can't paste a URL for the playground since the error happens only
>> when the code is loaded on node, not in a browser.
>>
>> --
>> Rule of Diversity: Distrust all claims for “one true way”. (Eric S.
>> Raymond, The Art Of Unix Programming)
>>
>>
>> --
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> ___
>> qooxdoo-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Node.js and qooxdoo statics
I'm developing an app using appjs+nodejs+qooxdoo. The main problem is SCOPE. Hard to say what's your problem, but warning about binding and scope ... I'm using lot's of qx.lang.Function.bind and var self = this; in my code. Don't know exactly what's your problem but just take care of binding/scope. On Mon, Sep 17, 2012 at 2:42 PM, Florin Jurcovici < [email protected]> wrote: > I have something like: > > qx.Class.define("test.ClassWithStatics", > { > statics: > { > constant1: "john", > constant2: "doe" > }, > > properties: > { > someProp: > { > init: test.ClassWithStatics.constant1, > check: [test.ClassWithStatics.constant1, > test.ClassWithStatics.constant2] > } > } > }); > > in a class which I compile into a qooxdoo app, and it works fine. > > However, when I try to use the same class on node.js (after having > required qooxdoo), I get: > > TypeError: Cannot read property 'constant1' of undefined > > at line "init: test.ClassWithStatics.constant1," when requiring > ClassWithStatics.js. > > Does anybody have any idea why? Is there a nice workaround, i.e. one > that shouldn't force me to move the constants out of > test.ClassWithStatics? > > I can't paste a URL for the playground since the error happens only > when the code is loaded on node, not in a browser. > > -- > Rule of Diversity: Distrust all claims for “one true way”. (Eric S. > Raymond, The Art Of Unix Programming) > > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] Node.js and qooxdoo statics
On 09/17/2012 02:42 PM, Florin Jurcovici wrote:
> I have something like:
>
> qx.Class.define("test.ClassWithStatics",
> {
> statics:
> {
> constant1: "john",
> constant2: "doe"
> },
>
> properties:
> {
> someProp:
> {
> init: test.ClassWithStatics.constant1,
> check: [test.ClassWithStatics.constant1,
> test.ClassWithStatics.constant2]
> }
> }
> });
>
> in a class which I compile into a qooxdoo app, and it works fine.
>
> However, when I try to use the same class on node.js (after having
> required qooxdoo), I get:
Did you install the NPM qooxdoo package? What does requiring qooxdoo
give you? How to you "try to use the same class on node.js"?
T.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi Christian,
if you take the newest download version, you will have the
qx = require('./qx-oo')
syntax. Thats what I prefer. :)
Regards,
Martin
Am 09.08.2010 um 20:46 schrieb panyasan:
>
> Hi Martin,
>
>
> MartinWittemann wrote:
>>
>>> be solved differently. How did you import qx-oo as a module in node.js?
>>
>> I just used the require statement and did not assign the return value of
>> it to qx. As the qx-oo script defines a global qx variable, it is not
>> necessary to assign it. But the way you used it is more the way it would
>> be used in node so I simply check how to include it in the loader
>> template... shouldn't be a problem.
>>
>
> but I still wonder - should it be:
>
> qx = require('./qx-oo').qx;
>
> or rather:
>
> qx = require('./qx-oo');
>
> The first needs "exports.qx = qx", the second "exports = qx;". I like the
> second option better, but the node.js dev's councel against replacing the
> "exports" variable entirely with a custom object.
>
> C.
> --
> View this message in context:
> http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5390139.html
> Sent from the qooxdoo mailing list archive at Nabble.com.
>
> --
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> ___
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
--
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi Martin,
MartinWittemann wrote:
>
>> be solved differently. How did you import qx-oo as a module in node.js?
>
> I just used the require statement and did not assign the return value of
> it to qx. As the qx-oo script defines a global qx variable, it is not
> necessary to assign it. But the way you used it is more the way it would
> be used in node so I simply check how to include it in the loader
> template... shouldn't be a problem.
>
but I still wonder - should it be:
qx = require('./qx-oo').qx;
or rather:
qx = require('./qx-oo');
The first needs "exports.qx = qx", the second "exports = qx;". I like the
second option better, but the node.js dev's councel against replacing the
"exports" variable entirely with a custom object.
C.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5390139.html
Sent from the qooxdoo mailing list archive at Nabble.com.
--
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hello Burak, > what's going to be the license of qxoo, lgpl? it'd be wonderful if you > could release qxoo under bsd license. As its part of qooxdoo and contains only a part of the whole qooxdoo code, I guess we don't change the license of it. Additionally, I don't think we are going to "release" is anyway. Its just a tiny generator job which wraps up the right parts of qooxdoo. Regards, Martin -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
On 08/09/10 09:12, Martin Wittemann wrote: > Hello Christian, > >> much more readable now! > Totally agree! Thats really looking good, but still I have to get used to see > qooxdoo code run on a server. :) > >> What I had to do to make this work is to add "exports.qx = qx;" at >> the end of the qx-oo.js file. Is that something that could be added to the >> file by default? Or a special job "build-qx-oo-node-js"? But maybe this can >> be solved differently. How did you import qx-oo as a module in node.js? > I just used the require statement and did not assign the return value of it > to qx. As the qx-oo script defines a global qx variable, it is not necessary > to assign it. But the way you used it is more the way it would be used in > node so I simply check how to include it in the loader template... shouldn't > be a problem. > hi, what's going to be the license of qxoo, lgpl? it'd be wonderful if you could release qxoo under bsd license. best, burak -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hello Christian, > much more readable now! Totally agree! Thats really looking good, but still I have to get used to see qooxdoo code run on a server. :) > What I had to do to make this work is to add "exports.qx = qx;" at > the end of the qx-oo.js file. Is that something that could be added to the > file by default? Or a special job "build-qx-oo-node-js"? But maybe this can > be solved differently. How did you import qx-oo as a module in node.js? I just used the require statement and did not assign the return value of it to qx. As the qx-oo script defines a global qx variable, it is not necessary to assign it. But the way you used it is more the way it would be used in node so I simply check how to include it in the loader template... shouldn't be a problem. Regards, Martin -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Another update: Using Martin's qx-oo.js package, I have turned the server script into a real qooxdoo class (rev. 20611). Goodbye, coding by closure (It is really a pain to code javascript the old way once you have started qooxdoo development)! compare http://qooxdoo-contrib.svn.sourceforge.net/viewvc/qooxdoo-contrib/trunk/qooxdoo-contrib/NodeSocket/trunk/demo/default/socket/server.js?revision=20611&view=markup with the old http://qooxdoo-contrib.svn.sourceforge.net/viewvc/qooxdoo-contrib/trunk/qooxdoo-contrib/NodeSocket/trunk/demo/default/socket/server.js?revision=20608&view=markup much more readable now! @Martin: What I had to do to make this work is to add "exports.qx = qx;" at the end of the qx-oo.js file. Is that something that could be added to the file by default? Or a special job "build-qx-oo-node-js"? But maybe this can be solved differently. How did you import qx-oo as a module in node.js? -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5383720.html Sent from the qooxdoo mailing list archive at Nabble.com. -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Thanks Christian! I'll probably take a look at it this we :) Regards, Benoît. -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5379944.html Sent from the qooxdoo mailing list archive at Nabble.com. -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Further update: I just checked in the NodeSocket Contribution into qooxdoo-contrib: http://qooxdoo-contrib.svn.sourceforge.net/viewvc/qooxdoo-contrib/trunk/qooxdoo-contrib/NodeSocket/trunk/ Here's a screenshot: http://qooxdoo.678.n2.nabble.com/file/n5379905/Bild_1.png If you look at the server code: http://qooxdoo-contrib.svn.sourceforge.net/viewvc/qooxdoo-contrib/trunk/qooxdoo-contrib/NodeSocket/trunk/demo/default/socket/server.js?revision=20608&view=markup and see how little code is necessary to make this work, you might understand why I am so excited about this technology. BTW, I used the new virtual list to keep up an up-to-date member list on all clients. Unfortunately, the socket.IO code uses "for( var i in array)" instead of "for ( var i=0; i< array.length; i++)" which doesn't seem to work with qooxdoo, so I had to patch the socket.io code and ship it with the contrib -- which is more comfortable for trying it out - but I don't know about the compatibility of the MIT licence with the qooxdoo licenses. Probably in the released version, the socket.io code should be downloaded separately. I don't have time to provide a public demo, so if you're interested, you'll need to download and install the demo yourself. Here's the readme: Node.js/Socket.io Wrapper = This contribution wraps the Socket.IO event transport for use in qooxdoo. See http://socket.io/ Of course, you can use Socket.IO directly without this wrapper. What this contribution does is to integrate the Socket.IO events into the qooxdoo message bus so that there is a uniform message passing system that bridges the server-client gap. This also means that the underlying implementation can be easily switched without any code change. See the demo for your usual chat application. Installation: = - Install the node.js server as instructed at http://www.nodejs.org/ - Currently, all files from the Socket.IO project are shipped with the contrib. since they have to be slightly patched to work with qooxdoo. - If you plan to do "source" development, make a symlink to the qooxdoo sdk inside the top-level release version folder (for example, "0.1" or "trunk". The reason is that the shipped node.js-server doesn't serve files outside this folder. Run the demo: - If you just want to run the demo, adapt the config.json file and point the QOOXDOO_PATH constant to the path of the qooxdoo sdk. - Run ./generate.py build in the demo/default folder - Go to demo/default/server/ and start the server with 'node server.js' - Load http://localhost:8088/demo/default/build/index.html in several browser windows. - Chat with yourself ;-) Known Issues/To Do == - The demo has only been tested with the latest Safari and Chrome, which both support web sockets. Is is currently not working with Firefox because of some issues with the WebSocket Flash applet. - The static file server is fast, but inefficient because it doesn't do any caching. There are several static file servers for node.js which should be integrated to make it more efficient. This is only the first step. Next is getting a JSONRPC server working. Hope you enjoy this little demo app. Cheers, Christian -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5379905.html Sent from the qooxdoo mailing list archive at Nabble.com. -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
MartinWittemann wrote:
>
> But anyway, I have good news! I took two hours yesterday right after the
> release to play a bit with building a file containing only the qooxdoo OO
> layer which can be used in webworkers, on servers (Rihno and node.js) and
> so on. I managed to get it done and will include it in the framework:
> http://bugzilla.qooxdoo.org/show_bug.cgi?id=3965
>
That is great news. I am making progress with the node/socket.io contrib and
will test it as soon as I can.
Some preliminary report: Socket.IO seems to be robust, but the API is a bit
undercomplex compared with the qooxdoo event/message system. I have
configured it so that you can open a channel to the server with
socket.addChannel("my/channel/*"), which will catch all messages that match
the channel name (using the wildcard system of
qx.event.message.Bus.subscribe). By default, all messages that are sent to
the server will be broadcast to all clients and dispatched as
qx.event.message.Message objects. Thus, so far, it is not possible to
subscribe only to selected channels, just to subscribe to selected messages
on the client itself.
As a demo, I am porting the chat client form the cometd contrib to the new
system. The amount of code needed to implement this demo is incredibly small
using this system, which appears to prove to me that I am on the right
track. Of course, I am still open to be proven wrong.
The server is really lightweight - CPU usage is far below what I am seeing
with Apache/PHP. Serving static files is fast. What needs to be implemented
is a simple caching system so that the server doesn't resend the full static
files on each request. I probably shouldn't reinvent the wheel here and use
one of the static file servers that are offered as a module to node.js,
since I also do not know how caching really works in the http protocol.
Most importantly, one cannot build a backend only on message-passing
(although this is a very fine thing), that is, we do still need the
additional json-rpc server. Martin said that his implementation wouldn't
work with newer releases of node.js -- Martin, can you be more specific
about this?
Finally, two question concerning qooxdoo-contrib:
- Locally, I have created a "Node" folder, containing the "Socket" project
with source and demo, the idea being that it might make sense to group all
node.js projects together. When I check the code in, I can either keep this
structure or move the "Socket" project to the top-level. I would assume you
prefer the latter, but let me know.
- I am going to abandon the cometd project because I think it is a dead-end,
and I see no future for it unless someone rewrites it from scratch. Should
it still be part of qooxdoo-contrib or should I delete it? It is unusable as
it is now.
Cheers,
Christian
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5375769.html
Sent from the qooxdoo mailing list archive at Nabble.com.
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
___
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hey, sorry guys, I didn't have the time to read all your mails so I'm not sure whats going on. But anyway, I have good news! I took two hours yesterday right after the release to play a bit with building a file containing only the qooxdoo OO layer which can be used in webworkers, on servers (Rihno and node.js) and so on. I managed to get it done and will include it in the framework: http://bugzilla.qooxdoo.org/show_bug.cgi?id=3965 Best, Martin Am 03.08.2010 um 11:05 schrieb panyasan: > > > panyasan wrote: >> >> leverage a technology (qooxdoo/javascript) and there is a way to extend it >> to the client in a simple and > > "extend it to the SERVER", that is... > > C. > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5367495.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > -- > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
panyasan wrote: > > leverage a technology (qooxdoo/javascript) and there is a way to extend it > to the client in a simple and "extend it to the SERVER", that is... C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5367495.html Sent from the qooxdoo mailing list archive at Nabble.com. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hello, this has become an interesting discussion. But in the end: everyone starts with different experiences and investments into technologies that need to be most efficiently applied to the problem at hand. If I can leverage a technology (qooxdoo/javascript) and there is a way to extend it to the client in a simple and straightforward way, and there is a way this can solve the requirement of the SPECIFIC app I have in mind (not all applications that anyone else might need to implement), then there is no need to learn yet another language and application framework. node.js might not be up to the task, but maybe it is. Who knows. It's an empirical question, not a theoretical one. So let's try it and create one MORE solution to the backend problem, not THE solution. Cheers, C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5367411.html Sent from the qooxdoo mailing list archive at Nabble.com. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi. > Threads are a debugging and maintenance nightmare. (...) > I recommend against using them for nearly all applications. You can't resonably expect an app server talking to several databases simultaneously and serving up thousands of clients could do without threads. You also can't reasonably expect that your web app running on that app server could ignore these issues. However, I agree that you should be able to leave most of threads-related issues to a framework, and not do all nitty-gritty housekeeping yourself. I think, however, that a language/platform not providing access to the threading mechanism would be crippled. ASP.Net does try this, and I really dislike what you have to do there. >> performance/memory footprint is problem, I still have to see something like this. However, since there's no widely deployed server-side javascript-based solution around, we can't really know. Java and C#/.Net have very smart optimization mechanisms for app servers, which Javascript couldn't possibly have, due to lack of static typing and proper linking, for instance. I'm pretty sure, however, that once it's a problem, alternative optimizing approaches would evolve. > Type-safe is highly over-rated. You wish! Type safety stems from static typing, and static typing has nothing to do (well, maybe just a little) with mem allocation nowadays. It has to do with the compiler being able to detect heaps of errors way before you even thought about writing a unit test, and with the IDE being able to provide stuff like autocompletion. In large projects, it's a very useful feature. Tell me you never wanted to have proper intellisense in Javascript code. >> and there are no libraries. But there are contribs :) > My biggest problem with JavaScript as a language is its non-standard > prototype-based object model. How so? Javascript's prototype-based model is standard ECMA 626, and has reached version 3. Last time I looked, it was planned that version 4 will be skipped and version 5 will contain some static typing mechanisms, and other features to make it look more like a more traditional OO language. The fact that most OO languages out there use a class-based rather than a prototype-based approach to OO doesn't mean that a prototype-based approach is less worthy. > Personally I think that > javascript is so much used now only because there is no other choice. I don't think so. Especially nowadays flexibility of a language is becoming more and more important. Show me a single language more flexible than Javascript, without the obvious formatting drawbacks of python (no IDE can properly reformat python sources with scrambled indents, whereas Javascript doesn't suffer from this). IMO, once Javascript breaks the browser jail, and interpreters start properly implementing the new ECMA-262 v5 standard, or may be an even newer standard, which adds static typing and linking features to the language, Javascript will become a lot more usable, and will be increasingly used in larger projects. br, flj -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Ok, we're now marching straight into a religious war about languages - if I would be heeding what my grandmother used to say - never ever discuss sex, religion and programming languages - I would remain silent. But tongue in cheek away, let's expand a little bit on a specific part of that discussion: - JS is a single threaded language - threads are a debugging nightmare True, so how does one cope with the implicit parallelism GUIs in general push into the users hand, the implicit parallelism a web server has to have by dealing with multiple connections, the implicit parallelism an MVC model with a middle layer (yes, I actually read that article and its predecessors) exposes? The world is parallel and programming languages/frameworks/systems are generally badly equipped to deal with parallelism in general. It was a relief for me when I hit twisted many years ago, not because of it being a huge and complicated beast, but because of the most beautifully implemented concept of a deferred programming style which is the foundation of twisted. For a short and sweet intro see http://krondo.com/blog/?p=1778 if you want to dig a little deeper http://twistedmatrix.com/documents/current/core/howto/defer.html After all I've done with using deferreds in programming for the last few years I can only say that I couldn't have done it with any other language/framework/system in existence. So, for me it's not a matter of choosing the 'right' programming language/system/framework it's a matter of what concepts are implemented in those elements. And this is the promising part of node.js, that it was influenced by and carries such concepts perhaps a little further. So, what am I missing from node.js? - clean Windows support (if one wants to live off writing software one cannot ignore Windows as deployment platform) - way too complex addon writing (me having quite some code which can and will not be transported into other languages) - much more clarity in expressing /forcing?) parallel concepts like deferred chaining, deferred action lists - banning synchronous calls altogether - more protocol implementations For me it's observing node.js from the sidelines, but up till now it's not yet fit to take over from twisted/nevow Werner On 02.08.2010 22:44, Petr Kobalíček wrote: Hi Derrell, On Mon, Aug 2, 2010 at 9:28 PM, Derrell Lipman mailto:[email protected]>> wrote: On Mon, Aug 2, 2010 at 14:58, Petr Kobalíček mailto:[email protected]>> wrote: Hi, do you think that javascript is a good language to use it on server-side? For me it's worst language I ever worked with, but there is no other I can use to write multibrowser web-pages / web-apps. Different strokes for different folks. Having used many languages over the past 1/4 century, JavaScript is currently my favorite of any I've ever used. It's my opinion, not common truth. Javascript is singlethreaded language, Good. Threads are a debugging and maintenance nightmare. Been there, done that. I recommend against using them for nearly all applications. (They do have appropriate uses; I just feel they're way overused when it is inappropriate, and many developers who attempt to use them don't have the skill set to do so properly.) There are better mechanisms to use in most cases: heavy-weight processes if they're not fired up too frequently; an event loop (often a great solution); etc. I'm talking about the design of language. It's always good if you have choice than if you don't. It's more easier if language allows you to do things. performance/memory footprint is problem, Performance, possibly. With the latest JIT JavaScript interpreters, I'm not even sure if that's much of an issue any longer. Memory footprint is not an issue in anything but embedded systems (memory is practically free, and computers come with lots of it), and even in the embedded environment I'd have to do some experimenting to see whether the memory footprint really greatly exceeds (or exceeds to an untenable extent) the footprint of a compiled application. I understand x86/x64 assembler very much and I can say that no jit can generate code that is similar to C/C++ (the most efficient languages when it comes to performance). I have no problem with this, because C++ compiler spend much more time when compiling code to machine. My problem here is that Java or .NET compilers can create much better jit-code than javascript without extra cost - type information is known, class memory structure and members are known - there is not guess whether type is int, string or class, the compiler simply knows all types except type-casted objects. Currently javascript jit compilers are doing extra work to guess correct type, they are patching code, tracing code - the design of language seems to be more complic
Re: [qooxdoo-devel] node.js and qooxdoo
Hi. Javascript has its advantages. Neither C# nor Java provide the same level of flexibility. And it's definitely not the worst language I ever worked with. In fact, it's one of the better ones. A Javascript version with optional static typing plus mechanisms for aspects, generics, operator overloading in the language itself, not added by some framework on top of the language (besides some stuff not being possible without language support), would IMO be the ideal language for both server and client scripting. Without such features, creating larger enterprise apps and properly testing them is somewhat more tedious than it should be. The UI is something different - there you actually see exactly what you're doing. When it comes to the server side what you're doing and what happens isn't that obvious anymore, and the language limitations become more obvious. Just my opinion. br, flj -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi. > no one > running a high-traffic site is choosing apache these days at the front > line. I wouldn't say so. A quick googling says something else: http://durak.org/sean/pubs/bss/ http://www.e-gineer.com/v1/articles/web-servers-used-at-the-top-sites.htm For me, node.js is interesting in order to be able to qu ickly patch together an app working offline while still u sing qooxdoo. I can't imagine node.js being used as an actual dedicated web server for an enterprise application. Besides being somewhat new, and thus probably a nono for most companies, most companies have already settled on a web application delivery platform, which is most likely not node.js. However, in spite of web access becoming ubiquitous, there are still requirements for clients which can work both online and offline. With node.js behind it, qooxdoo becomes a solution for such apps too. br, flj -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi Derrell, On Mon, Aug 2, 2010 at 9:28 PM, Derrell Lipman < [email protected]> wrote: > On Mon, Aug 2, 2010 at 14:58, Petr Kobalíček wrote: > >> Hi, >> >> do you think that javascript is a good language to use it on server-side? >> For me it's worst language I ever worked with, but there is no other I can >> use to write multibrowser web-pages / web-apps. >> > > Different strokes for different folks. Having used many languages over the > past 1/4 century, JavaScript is currently my favorite of any I've ever used. > It's my opinion, not common truth. Javascript is singlethreaded language, > > > Good. Threads are a debugging and maintenance nightmare. Been there, done > that. I recommend against using them for nearly all applications. (They do > have appropriate uses; I just feel they're way overused when it is > inappropriate, and many developers who attempt to use them don't have the > skill set to do so properly.) There are better mechanisms to use in most > cases: heavy-weight processes if they're not fired up too frequently; an > event loop (often a great solution); etc. > I'm talking about the design of language. It's always good if you have choice than if you don't. It's more easier if language allows you to do things. performance/memory footprint is problem, > > > Performance, possibly. With the latest JIT JavaScript interpreters, I'm not > even sure if that's much of an issue any longer. Memory footprint is not an > issue in anything but embedded systems (memory is practically free, and > computers come with lots of it), and even in the embedded environment I'd > have to do some experimenting to see whether the memory footprint really > greatly exceeds (or exceeds to an untenable extent) the footprint of a > compiled application. > I understand x86/x64 assembler very much and I can say that no jit can generate code that is similar to C/C++ (the most efficient languages when it comes to performance). I have no problem with this, because C++ compiler spend much more time when compiling code to machine. My problem here is that Java or .NET compilers can create much better jit-code than javascript without extra cost - type information is known, class memory structure and members are known - there is not guess whether type is int, string or class, the compiler simply knows all types except type-casted objects. Currently javascript jit compilers are doing extra work to guess correct type, they are patching code, tracing code - the design of language seems to be more complicated than type-safe ones. Also javascript has no byte-code standardization, so it's nearly impossible to precompile some code and just import it by virtual-machine. There is also no language keyword to do it (because it was never designed to do so). it's not type-safe > > > Type-safe is highly over-rated. Types were necessary in early compiled > languages in order to tell the compiler how to allocate memory. Types do > allow hints to be given to the developer when something bad is assigned, but > I think the flexibility of, for example, storing numbers in some elements of > an array and strings or even object references in other elements far > outweigh the benefits of rigid types. > Type-safety build into language itself has its benefits. Look at actionscript for example, you have choice to use static types or dynamic ones. The minor side effect is that when you add type-info to your code it should be more efficient and compiler can tell you basic mistakes. This is impossible with javascript. > >> and there are no libraries. > > > That will likely change soon. In the interim, as with PHP, C libraries can > likely be linked in to provide external functionality. > I understand this, but since there is no standardization in javascript how to do it and there are more interpreters you can use on the server there can be situation that your library has no bindings for you. With PHP/Python/Java you have usually luck or these tools are written in a language itself. > > >> Personally I can't understand why to use qooxdoo on server side, what you >> gain? Using oo model, > > > My biggest problem with JavaScript as a language is its non-standard > prototype-based object model. qooxdoo has pretty much fixed that, giving it > a similar object model to other current and common languages. > Question is, is problem solved in right place? Adding type-safety and standard class system into language will solve this problem for all code, not just your code. Qooxdoo is its own world, you can't rewrite all javascript code to use qooxdoo object model. > >> Using dom or widgets, what is it good for? > > > Nothing. They likely have nothing to do with server-side JavaScript > programming. > Some node.js users are using jquery for example, so I asked;) > > I respect your opinion, and I believe it's a fairly common opinion. I also > see an evolution to a different (better, IMO) paradigm for many > applications, and JavaScript
Re: [qooxdoo-devel] node.js and qooxdoo
Well said, as usual. T. > On Mon, Aug 2, 2010 at 14:58, Petr KobalÃÄ�ek > wrote: > >> Hi, >> >> do you think that javascript is a good language to use it on >> server-side? >> For me it's worst language I ever worked with, but there is no other I >> can >> use to write multibrowser web-pages / web-apps. >> > > Different strokes for different folks. Having used many languages over the > past 1/4 century, JavaScript is currently my favorite of any I've ever > used. > > >> Javascript is singlethreaded language, > > > Good. Threads are a debugging and maintenance nightmare. Been there, done > that. I recommend against using them for nearly all applications. (They do > have appropriate uses; I just feel they're way overused when it is > inappropriate, and many developers who attempt to use them don't have the > skill set to do so properly.) There are better mechanisms to use in most > cases: heavy-weight processes if they're not fired up too frequently; an > event loop (often a great solution); etc. > > >> performance/memory footprint is problem, > > > Performance, possibly. With the latest JIT JavaScript interpreters, I'm > not > even sure if that's much of an issue any longer. Memory footprint is not > an > issue in anything but embedded systems (memory is practically free, and > computers come with lots of it), and even in the embedded environment I'd > have to do some experimenting to see whether the memory footprint really > greatly exceeds (or exceeds to an untenable extent) the footprint of a > compiled application. > > >> it's not type-safe > > > Type-safe is highly over-rated. Types were necessary in early compiled > languages in order to tell the compiler how to allocate memory. Types do > allow hints to be given to the developer when something bad is assigned, > but > I think the flexibility of, for example, storing numbers in some elements > of > an array and strings or even object references in other elements far > outweigh the benefits of rigid types. > > >> and there are no libraries. > > > That will likely change soon. In the interim, as with PHP, C libraries can > likely be linked in to provide external functionality. > > >> Personally I can't understand why to use qooxdoo on server side, what >> you >> gain? Using oo model, > > > My biggest problem with JavaScript as a language is its non-standard > prototype-based object model. qooxdoo has pretty much fixed that, giving > it > a similar object model to other current and common languages. > > >> Using dom or widgets, what is it good for? > > > Nothing. They likely have nothing to do with server-side JavaScript > programming. > > I respect your opinion, and I believe it's a fairly common opinion. I also > see an evolution to a different (better, IMO) paradigm for many > applications, and JavaScript on the server is part of that evolution. > > Derrell > -- > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
On Mon, Aug 2, 2010 at 14:58, Petr Kobalíček wrote: > Hi, > > do you think that javascript is a good language to use it on server-side? > For me it's worst language I ever worked with, but there is no other I can > use to write multibrowser web-pages / web-apps. > Different strokes for different folks. Having used many languages over the past 1/4 century, JavaScript is currently my favorite of any I've ever used. > Javascript is singlethreaded language, Good. Threads are a debugging and maintenance nightmare. Been there, done that. I recommend against using them for nearly all applications. (They do have appropriate uses; I just feel they're way overused when it is inappropriate, and many developers who attempt to use them don't have the skill set to do so properly.) There are better mechanisms to use in most cases: heavy-weight processes if they're not fired up too frequently; an event loop (often a great solution); etc. > performance/memory footprint is problem, Performance, possibly. With the latest JIT JavaScript interpreters, I'm not even sure if that's much of an issue any longer. Memory footprint is not an issue in anything but embedded systems (memory is practically free, and computers come with lots of it), and even in the embedded environment I'd have to do some experimenting to see whether the memory footprint really greatly exceeds (or exceeds to an untenable extent) the footprint of a compiled application. > it's not type-safe Type-safe is highly over-rated. Types were necessary in early compiled languages in order to tell the compiler how to allocate memory. Types do allow hints to be given to the developer when something bad is assigned, but I think the flexibility of, for example, storing numbers in some elements of an array and strings or even object references in other elements far outweigh the benefits of rigid types. > and there are no libraries. That will likely change soon. In the interim, as with PHP, C libraries can likely be linked in to provide external functionality. > Personally I can't understand why to use qooxdoo on server side, what you > gain? Using oo model, My biggest problem with JavaScript as a language is its non-standard prototype-based object model. qooxdoo has pretty much fixed that, giving it a similar object model to other current and common languages. > Using dom or widgets, what is it good for? Nothing. They likely have nothing to do with server-side JavaScript programming. I respect your opinion, and I believe it's a fairly common opinion. I also see an evolution to a different (better, IMO) paradigm for many applications, and JavaScript on the server is part of that evolution. Derrell -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi, do you think that javascript is a good language to use it on server-side? For me it's worst language I ever worked with, but there is no other I can use to write multibrowser web-pages / web-apps. Using java on server side and java applets/javafx on client is the same (same language for both server and client), similarly using Silverlight and .NET (for me at this time better solution than java based ones, because C# is very nice language). Javascript is singlethreaded language, performance/memory footprint is problem, it's not type-safe and there are no libraries. Personally I can't understand why to use qooxdoo on server side, what you gain? Using oo model, okay, but shouldn't be this solved by language itself? Using dom or widgets, what is it good for? If you are generating page you usually use some framework so you can access widgets and stuff like this. When writing web-app in qooxdoo then you write user-interface in javascript itself and you need only to transfer data. Again where is advantage of using qooxdoo on server-side? To map string -> string and list -> list? This can be done in Java/C#/Python/Ruby, etc... Just my two cents and personal opinions;) Best regards / S pozdravem Petr Kobalicek On Mon, Aug 2, 2010 at 7:30 PM, b a wrote: > On 8/2/10, thron7 wrote: > > twisted is certainly a proven platform. but as apache, it is rather for > > complex applications, and it's a huge and unwieldy beast. nothing > > compared to the ultra-light node.js. and performance-wise i think there > > is no way current python implementations can beat v8 and the likes, even > > if run through stackless or pypy. > > > > in fact, i have long waited to see js break out of the "browser jail" > > and quite like the thought of a unified ui layer stretching up to the > > server. i again recommend you to kyle simpsons article series about the > > "middle end" in jsmag (see [1] for an appetizer). > > > > I second this. > > Just imagine basically if you use Qooxdoo + Node.js you just use > Javascript, you don't need anything else, so just one language for > both server-side and client-side. > > Plus, node.js doesn't require a thousand config files and stuff like > that, you just write the server you need quickly in javascript. > > And you get the full power of js, it's pretty awesome. > > > -- > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
On 8/2/10, thron7 wrote: > twisted is certainly a proven platform. but as apache, it is rather for > complex applications, and it's a huge and unwieldy beast. nothing > compared to the ultra-light node.js. and performance-wise i think there > is no way current python implementations can beat v8 and the likes, even > if run through stackless or pypy. > > in fact, i have long waited to see js break out of the "browser jail" > and quite like the thought of a unified ui layer stretching up to the > server. i again recommend you to kyle simpsons article series about the > "middle end" in jsmag (see [1] for an appetizer). > I second this. Just imagine basically if you use Qooxdoo + Node.js you just use Javascript, you don't need anything else, so just one language for both server-side and client-side. Plus, node.js doesn't require a thousand config files and stuff like that, you just write the server you need quickly in javascript. And you get the full power of js, it's pretty awesome. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Qooxdoo is a huge beast too. Means it something;-)? On Mon, Aug 2, 2010 at 7:16 PM, thron7 wrote: > twisted is certainly a proven platform. but as apache, it is rather for > complex applications, and it's a huge and unwieldy beast. nothing > compared to the ultra-light node.js. and performance-wise i think there > is no way current python implementations can beat v8 and the likes, even > if run through stackless or pypy. > > in fact, i have long waited to see js break out of the "browser jail" > and quite like the thought of a unified ui layer stretching up to the > server. i again recommend you to kyle simpsons article series about the > "middle end" in jsmag (see [1] for an appetizer). > > t. > > [1] http://blog.getify.com/2010/07/what-exactly-is-the-middle-end/ > > On 08/02/2010 06:58 PM, Werner Thie wrote: > > Can't resist to point out that what you're aiming at exists with > > twisted/nevow on the server side in python and athena/qooxdoo on the > > client side. > > > > - proven standalone webserver, http/https > > - probably the oldest and widest protocol support for TCP/IP in Python > > - completely asynchronous framework (deferreds) for Python and JScript > > - cross object instantiation (Python/Jscript) > > - clean cross object RPC > > - dynamic widget injection/removal > > - concise and clean OO > > - an import system for JScript letting you modularize JS > > > > If it must be JScript on the server side then why not have a closer look > > at clean asynchronous programming with deferreds before embarking on > > such a journey. > > > > My 2cts, Werner > > > > http://twistedmatrix.com/trac/ > > http://divmod.org/trac > > > > Burak Arslan wrote: > >> On 08/02/10 17:36, b a wrote: > >>> On 8/2/10, benco wrote: > All Right. Yep indeed, in theory, node.js doesn't need another http > server. > > But I heard that, according to the creator, nodejs isn’t really ready > for > replacing http server yet - however, I don't know if it still the case > nowadays. > >>> I'm pretty sure it can succesfuly replace the HTTP server, it's just > >>> reading a file > >>> on disk and serving it.. not so hard. > >> > >> apache has years of experience dealing with dos attacks, broken clients, > >> malicious input etc. it's also the swiss army knife of web servers. you > >> can't throw all that away that easily. > >> > >> burak > >> > >> > >> > -- > >> The Palm PDK Hot Apps Program offers developers who use the > >> Plug-In Development Kit to bring their C/C++ apps to Palm for a share > >> of $1 Million in cash or HP Products. Visit us here for more details: > >> http://p.sf.net/sfu/dev2dev-palm > >> ___ > >> qooxdoo-devel mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > > > -- > > The Palm PDK Hot Apps Program offers developers who use the > > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > > of $1 Million in cash or HP Products. Visit us here for more details: > > http://p.sf.net/sfu/dev2dev-palm > > ___ > > qooxdoo-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > -- > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
twisted is certainly a proven platform. but as apache, it is rather for complex applications, and it's a huge and unwieldy beast. nothing compared to the ultra-light node.js. and performance-wise i think there is no way current python implementations can beat v8 and the likes, even if run through stackless or pypy. in fact, i have long waited to see js break out of the "browser jail" and quite like the thought of a unified ui layer stretching up to the server. i again recommend you to kyle simpsons article series about the "middle end" in jsmag (see [1] for an appetizer). t. [1] http://blog.getify.com/2010/07/what-exactly-is-the-middle-end/ On 08/02/2010 06:58 PM, Werner Thie wrote: > Can't resist to point out that what you're aiming at exists with > twisted/nevow on the server side in python and athena/qooxdoo on the > client side. > > - proven standalone webserver, http/https > - probably the oldest and widest protocol support for TCP/IP in Python > - completely asynchronous framework (deferreds) for Python and JScript > - cross object instantiation (Python/Jscript) > - clean cross object RPC > - dynamic widget injection/removal > - concise and clean OO > - an import system for JScript letting you modularize JS > > If it must be JScript on the server side then why not have a closer look > at clean asynchronous programming with deferreds before embarking on > such a journey. > > My 2cts, Werner > > http://twistedmatrix.com/trac/ > http://divmod.org/trac > > Burak Arslan wrote: >> On 08/02/10 17:36, b a wrote: >>> On 8/2/10, benco wrote: All Right. Yep indeed, in theory, node.js doesn't need another http server. But I heard that, according to the creator, nodejs isn’t really ready for replacing http server yet - however, I don't know if it still the case nowadays. >>> I'm pretty sure it can succesfuly replace the HTTP server, it's just >>> reading a file >>> on disk and serving it.. not so hard. >> >> apache has years of experience dealing with dos attacks, broken clients, >> malicious input etc. it's also the swiss army knife of web servers. you >> can't throw all that away that easily. >> >> burak >> >> >> -- >> The Palm PDK Hot Apps Program offers developers who use the >> Plug-In Development Kit to bring their C/C++ apps to Palm for a share >> of $1 Million in cash or HP Products. Visit us here for more details: >> http://p.sf.net/sfu/dev2dev-palm >> ___ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > -- > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
> apache has years of experience dealing with dos attacks, broken clients, > malicious input etc. it's also the swiss army knife of web servers. you > can't throw all that away that easily. OTOH, apache has more and more evolved into an application platform, and is much too big and too heavy for serving content efficiently. no one running a high-traffic site is choosing apache these days at the front line. in contrast, single-process event-loop multiplexing web server are gaining share, like lighttpd [1], and i see node.js in the same vein. yes, it takes a bit to make a piece of software solid, but i don't see why this should not happen to node.js. if everything goes well, node.js is the new lighttpd. t. [1] http://www.lighttpd.net/ -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Can't resist to point out that what you're aiming at exists with twisted/nevow on the server side in python and athena/qooxdoo on the client side. - proven standalone webserver, http/https - probably the oldest and widest protocol support for TCP/IP in Python - completely asynchronous framework (deferreds) for Python and JScript - cross object instantiation (Python/Jscript) - clean cross object RPC - dynamic widget injection/removal - concise and clean OO - an import system for JScript letting you modularize JS If it must be JScript on the server side then why not have a closer look at clean asynchronous programming with deferreds before embarking on such a journey. My 2cts, Werner http://twistedmatrix.com/trac/ http://divmod.org/trac Burak Arslan wrote: > On 08/02/10 17:36, b a wrote: >> On 8/2/10, benco wrote: >>> All Right. Yep indeed, in theory, node.js doesn't need another http server. >>> >>> But I heard that, according to the creator, nodejs isn’t really ready for >>> replacing http server yet - however, I don't know if it still the case >>> nowadays. >> I'm pretty sure it can succesfuly replace the HTTP server, it's just >> reading a file >> on disk and serving it.. not so hard. > > apache has years of experience dealing with dos attacks, broken clients, > malicious input etc. it's also the swiss army knife of web servers. you > can't throw all that away that easily. > > burak > > > -- > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
On 08/02/10 17:36, b a wrote: > On 8/2/10, benco wrote: >> All Right. Yep indeed, in theory, node.js doesn't need another http server. >> >> But I heard that, according to the creator, nodejs isn’t really ready for >> replacing http server yet - however, I don't know if it still the case >> nowadays. > > I'm pretty sure it can succesfuly replace the HTTP server, it's just > reading a file > on disk and serving it.. not so hard. apache has years of experience dealing with dos attacks, broken clients, malicious input etc. it's also the swiss army knife of web servers. you can't throw all that away that easily. burak -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
On 8/2/10, benco wrote: > All Right. Yep indeed, in theory, node.js doesn't need another http server. > > But I heard that, according to the creator, nodejs isn’t really ready for > replacing http server yet - however, I don't know if it still the case > nowadays. I'm pretty sure it can succesfuly replace the HTTP server, it's just reading a file on disk and serving it.. not so hard. > Benoît. > > > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5364268.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > -- > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi, panyasan wrote: > > actually, what I have in mind is to replace Apache altogether for the > node.js part > All Right. Yep indeed, in theory, node.js doesn't need another http server. But I heard that, according to the creator, nodejs isn’t really ready for replacing http server yet - however, I don't know if it still the case nowadays. Anyway, if it's just for preliminary tests purpose, I should be fine I suppose :). Regards, Benoît. -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5364268.html Sent from the qooxdoo mailing list archive at Nabble.com. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
the_sheriff wrote: > > lines 185-216 serve static qooxdoo files > http://github.com/wsdookadr/Q-Chess/blob/master/server/serv.js > Cool, thanks! Learning by example is the fastest way forward :-) C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5363575.html Sent from the qooxdoo mailing list archive at Nabble.com. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
On 08/02/2010 12:02 PM, panyasan wrote: > > Hi Benoît, > > actually, what I have in mind is to replace Apache altogether for the > node.js part. I have the feeling that small qooxdoo apps could do without > Apache if a server script based on node.js can supply all the files that are > needed for the initial loading of the client application, and then switch to > an event-driven bidirectional socket communication with the server plus > node.js-based json-rpc. > > I think this could server as a complete out-of-the-box client-server > solution. I have no idea if that would scale well, but for the kind of > applications I of which am thinking, this seems to be a much better solution > than resource-hungry Apache or other other backends. > > Any thoughts? +1 definitely. T. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
lines 185-216 serve static qooxdoo files http://github.com/wsdookadr/Q-Chess/blob/master/server/serv.js cheers On 8/2/10, panyasan wrote: > > Hi, > > this weekend I started experimenting with node.js and Socket.IO, in order to > implement a solution that will hook into the qx.event.message system > (replacing the cometd contribution which I will no longer maintain). It > didn't go as fast as I originally thought -- for example, when mixing the > socket functionality with static file server functionality to server the > initial qooxdoo files. However, I hope to be able to commit a > proof-of-concept soon. > > Cheers, > > Christian > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5363375.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > -- > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi Benoît, actually, what I have in mind is to replace Apache altogether for the node.js part. I have the feeling that small qooxdoo apps could do without Apache if a server script based on node.js can supply all the files that are needed for the initial loading of the client application, and then switch to an event-driven bidirectional socket communication with the server plus node.js-based json-rpc. I think this could server as a complete out-of-the-box client-server solution. I have no idea if that would scale well, but for the kind of applications I of which am thinking, this seems to be a much better solution than resource-hungry Apache or other other backends. Any thoughts? C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5363466.html Sent from the qooxdoo mailing list archive at Nabble.com. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi Christian, Thanks for the report. I don't know if it is your case but I've heard that using Apache as http server for node.js applications is not recommended/adapted. Nginx seems to be a better candidate. Maybe you could give it a try ? Best, Benoît. -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5363398.html Sent from the qooxdoo mailing list archive at Nabble.com. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi, this weekend I started experimenting with node.js and Socket.IO, in order to implement a solution that will hook into the qx.event.message system (replacing the cometd contribution which I will no longer maintain). It didn't go as fast as I originally thought -- for example, when mixing the socket functionality with static file server functionality to server the initial qooxdoo files. However, I hope to be able to commit a proof-of-concept soon. Cheers, Christian -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5363375.html Sent from the qooxdoo mailing list archive at Nabble.com. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi Dietrich, I've been using the mongodb and they are pretty solid. I had no luck with any of the mysql drivers. Our current project uses redis (a really database) and it works like a charm. Best Fabian On Thu, Jul 29, 2010 at 9:43 AM, Dietrich Streifert wrote: > > Hi Fabian, > > sorry for nipping into this thread: > > Are you using any DB modules/drivers with nodejs? > > Are there reliable implementations? Or is there something like odbc/jdbc > (nodejsdbc?) > > Thank you for your answer. > > Best regards.. > > > Am 29.07.2010 00:56, schrieb Fabian Jakobs: >> Hi Christian, >> >> I am still on the mailing list by i read only topics which catch my >> interest - like yours does :) >> >> my qxoo should still work and provides all OO features and most of >> qx.core and qx.lang. The qooxdoo version used is from January but this >> shouldn't matter much as this code usually doesn't change frequently. >> If you plan to use it let me know, maybe I can help you getting >> started. >> >> We are using node.js for a project at my new company as well and it >> works fantastic. Implementing e.g. server push using long polling is >> almost trivial. >> >> Best Fabian >> >> P.S. >> please CC answers to my private mail >> >> On Wed, Jul 28, 2010 at 7:46 PM, panyasan wrote: >>> Cool. I KNEW that the smart qooxdoo devs/community must have already >>> noticed. >>> ;-) >>> >>> >>> MartinWittemann wrote: Hello Christian, sure I have thought about such scenarios. I have tested node.js also and was impressed by its elegance. I once wrote a full JSON RPC layer for node.js which is on my github account [1]. But i'm sure it's not working anymore because ryan (node JS guru) removed the promises one day. >>> Can you elaborate on what exactly they changed? >>> >>> I'll look into Fabian's code - is he still on the ML and can comment? >>> >>> Thanks, >>> >>> Christian >>> -- >>> View this message in context: >>> http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5346009.html >>> Sent from the qooxdoo mailing list archive at Nabble.com. >>> >>> -- >>> The Palm PDK Hot Apps Program offers developers who use the >>> Plug-In Development Kit to bring their C/C++ apps to Palm for a share >>> of $1 Million in cash or HP Products. Visit us here for more details: >>> http://p.sf.net/sfu/dev2dev-palm >>> ___ >>> qooxdoo-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >>> >> -- >> The Palm PDK Hot Apps Program offers developers who use the >> Plug-In Development Kit to bring their C/C++ apps to Palm for a share >> of $1 Million in cash or HP Products. Visit us here for more details: >> http://p.sf.net/sfu/dev2dev-palm >> ___ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > -- > Mit freundlichen Grüßen > Dietrich Streifert > -- > Visionet GmbH > Firmensitz: Am Weichselgarten 7, 91058 Erlangen > Registergericht: Handelsregister Fürth, HRB 6573 > Geschäftsführer: Stefan Lindner > > > > > -- > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
started writing a chess game server in node.js and qooxdoo on front-end http://github.com/wsdookadr/Q-Chess On 7/28/10, panyasan wrote: > > Hi, > > I am currently looking into node.js (http://nodejs.org/) and am pretty > fascinated, actually thinking to creating some of my backend logic with > node.js rather than with my usual PHP. > > Obviously, node.js cries out for a qx module providing all of the fine > OO-stuff that qooxdoo excels in. > > Also, it would be a big plus to have a RPCNodeJs server - promising faster > response times than the Apache/PHP solution (I don't know about the rest). > > Alternatively, a cometd-like solution (which already exists for node.js) > could bypass the jsonrpc transport altogether and implement client-server > communication on a very high level with subcribe/publish model - which > sounds even more attractive. This also seems like a natural fit for the > upcoming client-server databinding. > > Has anyone thought about this already or maybe even implemented something? > > C. > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5345772.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > -- > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi Fabian, sorry for nipping into this thread: Are you using any DB modules/drivers with nodejs? Are there reliable implementations? Or is there something like odbc/jdbc (nodejsdbc?) Thank you for your answer. Best regards.. Am 29.07.2010 00:56, schrieb Fabian Jakobs: > Hi Christian, > > I am still on the mailing list by i read only topics which catch my > interest - like yours does :) > > my qxoo should still work and provides all OO features and most of > qx.core and qx.lang. The qooxdoo version used is from January but this > shouldn't matter much as this code usually doesn't change frequently. > If you plan to use it let me know, maybe I can help you getting > started. > > We are using node.js for a project at my new company as well and it > works fantastic. Implementing e.g. server push using long polling is > almost trivial. > > Best Fabian > > P.S. > please CC answers to my private mail > > On Wed, Jul 28, 2010 at 7:46 PM, panyasan wrote: >> Cool. I KNEW that the smart qooxdoo devs/community must have already noticed. >> ;-) >> >> >> MartinWittemann wrote: >>> Hello Christian, >>> sure I have thought about such scenarios. I have tested node.js also and >>> was impressed by its elegance. I once wrote a full JSON RPC layer for >>> node.js which is on my github account [1]. But i'm sure it's not working >>> anymore because ryan (node JS guru) removed the promises one day. >>> >> Can you elaborate on what exactly they changed? >> >> I'll look into Fabian's code - is he still on the ML and can comment? >> >> Thanks, >> >> Christian >> -- >> View this message in context: >> http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5346009.html >> Sent from the qooxdoo mailing list archive at Nabble.com. >> >> -- >> The Palm PDK Hot Apps Program offers developers who use the >> Plug-In Development Kit to bring their C/C++ apps to Palm for a share >> of $1 Million in cash or HP Products. Visit us here for more details: >> http://p.sf.net/sfu/dev2dev-palm >> ___ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> > -- > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- Mit freundlichen Grüßen Dietrich Streifert -- Visionet GmbH Firmensitz: Am Weichselgarten 7, 91058 Erlangen Registergericht: Handelsregister Fürth, HRB 6573 Geschäftsführer: Stefan Lindner -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hello Christian, as far as i can say, it's currently not a topic here in the office. All my interests are based on a some nerdy thought. ;) But opening a bug is still a good idea even if i don't expect us to take care of it in the future, at least not this year for sure. Maybe someone has too much spare time and takes care of it, who knows. :D Regards, Martin Am 29.07.2010 um 08:38 schrieb panyasan: > > > Fabian Jakobs wrote: >> >> Hi Christian, >> >> I am still on the mailing list by i read only topics which catch my >> interest - like yours does :) >> >> my qxoo should still work and provides all OO features and most of >> qx.core and qx.lang. The qooxdoo version used is from January but this >> shouldn't matter much as this code usually doesn't change frequently. >> If you plan to use it let me know, maybe I can help you getting >> started. >> >> We are using node.js for a project at my new company as well and it >> works fantastic. Implementing e.g. server push using long polling is >> almost trivial. >> > > This is good to know. Since so much work has already been done, wouldn't it > be worth to create a meta bug with the aim to create a whole > "qooxdoo-node.js stack" of interoperable components in qooxdoo-contrib > (rather than in private vcs)? > > I think this should be a coordinated issue rather than lots of random > implementation attempts. It would certainly add a whole new dimension to the > question of a backend for qooxdoo: > > - an extremely lightweight server that is easy to install without many > prerequisites (as long as you're not on Winodws) > - the ability to work in the same language and with the same class > architecture on the server and client > - a potential for unified backend architecture for demos -- think of a > playground with a "client" and a "server" editor!!! > - finally a server-push/cometd-solution for qooxdoo that would integrate > naturally into the framework > > I don't expect this to materialize any time soon, but I'd be thrilled if the > devs would look at this as a future priority. I'd certainly be happy to > contribute. > > Christian > > > Fabian Jakobs wrote: >> >> P.S. please CC answers to my private mail >> > > I am using nabble (which seems to have a hiccup at the moment - it is not > displaying my messages and I saw your message only on sf.net) which doesn't > have CC, sorry! > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5346946.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > -- > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Fabian Jakobs wrote: > > Hi Christian, > > I am still on the mailing list by i read only topics which catch my > interest - like yours does :) > > my qxoo should still work and provides all OO features and most of > qx.core and qx.lang. The qooxdoo version used is from January but this > shouldn't matter much as this code usually doesn't change frequently. > If you plan to use it let me know, maybe I can help you getting > started. > > We are using node.js for a project at my new company as well and it > works fantastic. Implementing e.g. server push using long polling is > almost trivial. > This is good to know. Since so much work has already been done, wouldn't it be worth to create a meta bug with the aim to create a whole "qooxdoo-node.js stack" of interoperable components in qooxdoo-contrib (rather than in private vcs)? I think this should be a coordinated issue rather than lots of random implementation attempts. It would certainly add a whole new dimension to the question of a backend for qooxdoo: - an extremely lightweight server that is easy to install without many prerequisites (as long as you're not on Winodws) - the ability to work in the same language and with the same class architecture on the server and client - a potential for unified backend architecture for demos -- think of a playground with a "client" and a "server" editor!!! - finally a server-push/cometd-solution for qooxdoo that would integrate naturally into the framework I don't expect this to materialize any time soon, but I'd be thrilled if the devs would look at this as a future priority. I'd certainly be happy to contribute. Christian Fabian Jakobs wrote: > > P.S. please CC answers to my private mail > I am using nabble (which seems to have a hiccup at the moment - it is not displaying my messages and I saw your message only on sf.net) which doesn't have CC, sorry! -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5346946.html Sent from the qooxdoo mailing list archive at Nabble.com. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi Christian, I am still on the mailing list by i read only topics which catch my interest - like yours does :) my qxoo should still work and provides all OO features and most of qx.core and qx.lang. The qooxdoo version used is from January but this shouldn't matter much as this code usually doesn't change frequently. If you plan to use it let me know, maybe I can help you getting started. We are using node.js for a project at my new company as well and it works fantastic. Implementing e.g. server push using long polling is almost trivial. Best Fabian P.S. please CC answers to my private mail On Wed, Jul 28, 2010 at 7:46 PM, panyasan wrote: > > Cool. I KNEW that the smart qooxdoo devs/community must have already noticed. > ;-) > > > MartinWittemann wrote: >> >> Hello Christian, >> sure I have thought about such scenarios. I have tested node.js also and >> was impressed by its elegance. I once wrote a full JSON RPC layer for >> node.js which is on my github account [1]. But i'm sure it's not working >> anymore because ryan (node JS guru) removed the promises one day. >> > > Can you elaborate on what exactly they changed? > > I'll look into Fabian's code - is he still on the ML and can comment? > > Thanks, > > Christian > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5346009.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > -- > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Cool. I KNEW that the smart qooxdoo devs/community must have already noticed. ;-) MartinWittemann wrote: > > Hello Christian, > sure I have thought about such scenarios. I have tested node.js also and > was impressed by its elegance. I once wrote a full JSON RPC layer for > node.js which is on my github account [1]. But i'm sure it's not working > anymore because ryan (node JS guru) removed the promises one day. > Can you elaborate on what exactly they changed? I'll look into Fabian's code - is he still on the ML and can comment? Thanks, Christian -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5346009.html Sent from the qooxdoo mailing list archive at Nabble.com. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hello Christian, sure I have thought about such scenarios. I have tested node.js also and was impressed by its elegance. I once wrote a full JSON RPC layer for node.js which is on my github account [1]. But i'm sure it's not working anymore because ryan (node JS guru) removed the promises one day. So on a rewrite of the qooxdoo RPC layer we could use this code to provide a reference implementation of the RPC (which should cover the spec anyway). The qooxdoo OO system on node.js was a topic fabian took a look at some time ago on his github account [2]. I'm not sure how good this is still working. His approach was to manually set up a fire including all dependencies and therefore include these files. So we had a prove of concept that qx oo is working on a server but not much more. If you want to investigate more on this topic, let me know about it. I'm also very interested on all these possibilities with node.js. Best, Martin [1] http://github.com/wittemann/JSON-RPC-for-Node.js [2] http://github.com/fjakobs/qxoo -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5345871.html Sent from the qooxdoo mailing list archive at Nabble.com. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi Christian, Personally, I am also planning to migrate my PHP works to node.js - it looks really great! - but I'm not yet well familiar with it... so, all I can give to you for the moment is some links. Here is a list of (interesting) modules for/based on node.js : http://wiki.github.com/ry/node/modules You could have a look at this: http://socket.io/ (cross-browser websocket +node.js server solution) About "qooxdoo OO system" in node.js, the best would be to ask directly to Fabian Jackobs (because the http://github.com/fjakobs/qxoo project has not been updated since January) ... Best, Benoît. -- View this message in context: http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5345864.html Sent from the qooxdoo mailing list archive at Nabble.com. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] node.js and qooxdoo
Hi Christian, Please check it out: http://github.com/wittemann/JSON-RPC-for-Node.js http://github.com/fjakobs/qxoo But Martin and Fabian know better than me (it's their personal repositories). :) Cheers, Siarhei On Jul 28, 2010, at 6:38 PM, panyasan wrote: > > Hi, > > I am currently looking into node.js (http://nodejs.org/) and am pretty > fascinated, actually thinking to creating some of my backend logic > with > node.js rather than with my usual PHP. > > Obviously, node.js cries out for a qx module providing all of the fine > OO-stuff that qooxdoo excels in. > > Also, it would be a big plus to have a RPCNodeJs server - promising > faster > response times than the Apache/PHP solution (I don't know about the > rest). > > Alternatively, a cometd-like solution (which already exists for > node.js) > could bypass the jsonrpc transport altogether and implement client- > server > communication on a very high level with subcribe/publish model - which > sounds even more attractive. This also seems like a natural fit for > the > upcoming client-server databinding. > > Has anyone thought about this already or maybe even implemented > something? > > C. > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5345772.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > -- > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
