Ajax

Poster Content
nk4um Administrator
Posts: 158
November 7, 2006 19:47
The best selection among mechanism choices to link a browser to a NetKernel server is not something that we can recommend outside of a consulting engagement. That is because the actual choice must balance a range of (business and technological) risks that are only fully understood after deeper analysis. Having said that, from a technological perspective, an approach that removes artificial constraints seems better than one that imposes such constraints.

NetKernel is a general computing abstraction that can be easily adapted to a particular set of protocols, architectural styles, etc. So, you should not worry about NetKernel imposing constraints on your architectural options.

One of the principle benefits of NetKernel as an Ajax companion is the intrinsic caching and high-performance asynchronous internal processing. Whether you select a browser to server link that is limited in the number of connections or use a more generalized messaging scheme, it is not difficult to adapt and tune NetKernel to work very efficiently - especially as you increase the number of cores of CPUs in the computer.
Like · Post Reply
nk4um User
Posts: 31
November 7, 2006 17:31
Yes, that''s exactly the link, sorry, i forgot to deliver it.

Ok for NetKernel would have no problem supporting any new technologies which is near true for every product, the question is related to the article subject itself "XmlHttpRequest BAD - Messaging GOOD" so actual technology could answer the question if needed, for example all data manipulations and exchanges could be natively done in XML using standard HTTP verbs and data conversions to JSON could be done.

That were my question that we could divide in two parts :
- What is your opinion on the way doing Ajax ? XmlHttpRequest or the other messaging way (with the actual or old technology) ?

- Does NK have predispositions in its ajax management to handle things in conformity of this opinion ?
Like · Post Reply
nk4um Administrator
Posts: 607
November 7, 2006 16:13Correct link?
Is this the link you meant?
http://blogs.webtide.com/gregw/2006/10/18/1161164940000.html

Limitations of the using HTTP for fine grained asychronous messaging between browesr and server are well documented. However it is worth noting that low-level developer frustrations aside, AJAX has delivered a true general purpose cross platform rich web experience for users.

NetKernel would have no problem supporting any new technologies that became available with little effort. With so much uncertainty of how or when any replacement for AJAX comes about it isn''t possible to comment on how NetKernel would interface to it. I have every confidence that it is possible, though, given the disparate technologies integrated to date.

Dig into the core abstraction of NetKernel and gain this confidence for yourself! :-)
Like · Post Reply
nk4um User
Posts: 31
November 7, 2006 11:35Ajax
Regarding the way we doing Ajax applications, there is no much talk about the way we are implemented them. I were glad to see this article "XmlHttpRequest BAD - Messaging GOOD" http://www.active-endpoints.com/active-bpel-engine-overview.htm and as there is some concerns with NK, i would be pleased to have your opinions on the way NK proposes to handle this.
Like · Post Reply