Added to tutorials: Simple ItsNat (Core) STATELESS Application

[Jose Maria Arranz Santamaria]

The new tutorial is the same tutorial as the previously published in JavaLobby and a subset of the tutorial included in Reference Manual and online in the Feature Showcase.

Enjoy.

[Ravindranath Akila]

Neat! Thanks!

I actually went through the whole tutorial :-) and the online example.

Is the additional server cost more on RAM or CPU?

R. A.

On 14 Oct 2013 02:17, "Jose Maria Arranz Santamaria" <jmar...@innowhere.com> wrote:

The new tutorial is the same tutorial as the previously published in JavaLobby and a subset of the tutorial included in Reference Manual and online in the Feature Showcase.

Enjoy.

--
You received this message because you are subscribed to the Google Groups "itsnat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to itsnat+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Jose Maria Arranz Santamaria]

Hi Ravin

ItsNat stateful needs more RAM in average because in spite of DOM node caching shared between users, the user view is kept in server. CPU use is very low because when processing an AJAX event only the strictly necessary is done.

In stateless more CPU is needed when processing an AJAX event, because an ItsNatDocument must be loaded on the fly, more costly than stateful because in stateful AJAX events are smarter, however in stateless less memory is used because no user session data is needed in server (ItsNat point of view), memory just increases when an AJAX event hits the server but this memory is released when event ends, the pattern is more like sawtooth but much less in average.

And of course stateless mode opens you to horizontal scalability without session sync penalty or need of server affinity.  

For instance in Google App Engine, a cloud with no support of server affinity, stateless is the main option.

Regards

On 14/10/2013 1:25, Ravindranath Akila wrote:

Neat! Thanks!

I actually went through the whole tutorial :-) and the online example.

Is the additional server cost more on RAM or CPU?

R. A.

[Ravindranath Akila]

Since we don't have a server state anymore, can the DOM be meddled with by framework such as jQuery freely? Before, we needed to be a bit prudent over how we use frameworks that manipulate the DOM, but now I suspect we don't have to worry that much. Am I right?

On Tuesday, October 15, 2013 3:12:16 AM UTC+8, Jose Maria Arranz Santamaria wrote:

Hi Ravin

ItsNat stateful needs more RAM in average because in spite of DOM node caching shared between users, the user view is kept in server. CPU use is very low because when processing an AJAX event only the strictly necessary is done.

In stateless more CPU is needed when processing an AJAX event, because an ItsNatDocument must be loaded on the fly, more costly than stateful because in stateful AJAX events are smarter, however in stateless less memory is used because no user session data is needed in server (ItsNat point of view), memory just increases when an AJAX event hits the server but this memory is released when event ends, the pattern is more like sawtooth but much less in average.

And of course stateless mode opens you to horizontal scalability without session sync penalty or need of server affinity.  

For instance in Google App Engine, a cloud with no support of server affinity, stateless is the main option.

Regards

On 14/10/2013 1:25, Ravindranath Akila wrote:

Neat! Thanks!

I actually went through the whole tutorial :-) and the online example.

Is the additional server cost more on RAM or CPU?

R. A.

[Ravindranath Akila]

That's great news! I think now it's just a matter of being careful and not about limitations. I think most plug-ins would work (jQuery) if used prudently. Well, it is a whole new experience with stateless! And scalability does have a price

(Sorry, had dropped out the group mail id)

R. A.
BTW, there is a website called Thank God it's Friday!
It tells you fun things to do in your area over the weekend. 
See here: http://www.ThankGodItIsFriday.com

On 20 Oct 2013 23:45, "Jose Maria Arranz Santamaria" <jmar...@innowhere.com> wrote:

The answer is "much more freely" it depends how you're using ItsNat in stateless mode, in this mode ItsNat is very helpful for inserting new markup, and by using locById attribute, tolerance to "node pollution" by client centric JS tools is improved.

Regards