A timely question. :-) I have been looking at Web 2.0, node.js, jquery, and all the other javascript libraries coming out now.

It seems to me, that the general strategy is to find a way to do non-blocking I/O, so that one of your html div's dos'nt stall the whole page.

Of course, after playing around with a few Perl GUI libs, like Tk and Gtk2, you see the value of not having direct socket connection loops as your main loop. Instead, you run event-loop systems on both ends, both the socket and the server. The event-loops make and service the socket connections, so the sockets can be read or written to, in a non-blocking manner.

So, the whole idea of Web 2.0 is to break your monitor/screen into little divs( divisions), and each little div can run it's own javascript routine, automatically opening sockets and transferring information. So with event-loop based non-blocking I/O, many sockets can be simultaneously opened from your browser window, and be updating independently, without requiring an entire page refresh, you only need to refresh the div which originated the socket request.

The much heralded node.js is nothing more an eventloop system, written in javascript, which can handle JSON ( javascript object notation) packages of data. Furthermore, javascript itself is the eventloop running your browser. If you turn off javascript, you only prevent external scripts from being run, but the basic browser eventloop continues to run.

So..... if I was designing a general purpose strategy, it would be to be eventloop based, on both the server and client, AND the client should be able to be integrated into a web browser, which should be easy enough with javascript. It needs to handle things like I/O Promises, which is the eventloop's way of saying the "information is being readied for delivery".

Those are my current thoughts. :-)

I'm not really a human, but I play one on earth.
Old Perl Programmer Haiku ................... flash japh

In reply to Re: Current Thoughts on Server/Client Best Development Strategies by zentara
in thread Current Thoughts on Server/Client Best Development Strategies by rl4518

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.