I am not using jQuery, Catalyst…bloated nature. I require a bandwidth-efficient solution due to poor internet access…
Catalyst is only "bloated" in server-side RAM usage. Bandwidth does not come into it. jQuery is larger than several pure Ajax libs but smaller than plenty of others—minified and gzipped it's going to be a one time cost of around 30K—and if you use a version from a CDN like Google's, is guaranteed to be fast and depending on the clients, possibly already cached in the browser. Putting the most information in a single exchange, as opposed to direct triggering of snippets, is the most bandwidth friendly approach; unless you move to websockets or something similar (Corion had something related and neat here that I never followed-up to learn more about and can't quite remember. <- Update: I was remembering something that wouldn't be of help here).
Not saying your approach is inappropriate at all. Sometimes closer to the metal is necessary. Just wanted to balance the cat skinning considerations. :P
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
