On 11/15/2010 11:05 PM, Shamit Verma wrote: >> >> Yes and that's the reason I added in the initial response: >> >> > Where will the main 'engine' for the robot run ? on the robot's >> controller ? In >> > any case, for this use case you needn't touch java at all IMHO. All >> client side >> > stuff can be done using javascript. >> >> >> > This was not about controller, that would in any case be independent of UI. > Controller would be running on Robot and UI would be running inside a > browser. UI needs to talk to this controller and JS is not the best option > for that. JS restricts UI to http request/response based communication. >
Over-simplification much ? http://en.wikipedia.org/wiki/Comet_%28programming%29 http://en.wikipedia.org/wiki/Reverse_Ajax Umm, jtd's original post (and his replies) does not specify a controller independent of the UI. In fact, separating the two is also something that I suggested in my reply. In any case, blanket statements such as 'JS restricts UI to http request/response based communication' are not really useful. Did you see the NodeJS link I sent in the previous mail ? The index page itself has an example of running a TCP server using nodejs. > Communication within browser, is best handled in Java/Flex/Flash. > I'm not a huge JS fan myself, but I'm even less inclined to use client side Java applets to do UI stuff. btw, we've come a long way since the '90s cheers, - steve -- random spiel: http://lonetwin.net/ what i'm stumbling into: http://lonetwin.stumbleupon.com/ -- http://mm.glug-bom.org/mailman/listinfo/linuxers
