4 ms·
It's somewhat frustrating to me when they continuously say "something that's hard or impossible in other web frameworks is trivial in Lift". As one of the co-f
by asnyder 16y ago
It's somewhat frustrating to me when they continuously say "something that's hard or impossible in other web frameworks is trivial in Lift".
As one of the co-founders and developers of the NOLOH PHP Framework (http://www.noloh.com http://www.noloh.com), I know that we've had many of these features for quite some time, including Comet (we support all protocols including streaming, short-polling and long-polling) with little to no effort on the developer's part, and in many cases significantly less effort than described here in lift.
I have nothing against Lift, and clearly I'm bias, however, the tone should've been less hostile in my opinion. However, maybe the hostile tone is good marketing. It's hard to say.
- swannodette 16y agoWhat methods are you using to make Comet functionality scalable "without any effort" ?
- asnyder 16y agoYou can find extensive details regarding our thinking on Comet in our Comet slides from various conferences. http://www.slideshare.net/noloh/comet-by-pushing-server-data-we-push-the-web-forward http://www.slideshare.net/noloh/comet-by-pushing-server-data.... There's no way we can easily answer you with the "methods" we're using as we implement extensive original research. However, from a developer perspective it boils down to the developer specifying what they want to "Listen" to, and optionally how (streaming, short poll, long poll, etc) and NOLOH then takes care of the rest. For example, http://diffpaste.com/#/717/ http://diffpaste.com/#/717/. Philip Ross will be publishing an extensive white papers soon that goes into more academic depth if you're interested.
- simonw 16y agoHow do you implement scalable long polling and streaming in PHP? I've always been under the impression that you really need non-blocking IO to get that to work in a scalable fashion.
- asnyder 16y agoUnfortunately you'll have to wait until the white paper for details. Philip Ross has spent a significant amount of time and effort these past 2.5 years researching and implementing various solutions. I unfortunately can't summarize the solution in any succinct way, and fortunately/unfortunately he stays away from outlets such as HN (better for actually getting work done). However, I can promise you that as soon as he's done, I'll post it on HN and personally send you a message.