[whatwg] <a onlyreplace>

[tali garsiel]

 	<dd0fbad0910180717q60e0c0f5l12e81a337af57dc8 at mail.gmail.com> 

 	<BAY117-W9DABA5E3A74376FB4BBFC83C20 at phx.gbl>
 

 <dd0fbad0910180935i6b07e025t14f4cc5aaacb34a7 at mail.gmail.com>
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


I'll try to fix my example.
The table button is not "refresh" but a "next" button that keeps track of the table navigation.

That is a valid use case , isn't it? (at least by your first suggestion). You still wouldn't want the server to do any heavy calculation except for the data that needs to be displayed.

I tried to find an extreme use case but even showing the navigation panels often evolves lots of server work.
Examples can be license and permission checks for an entire tree and parsing xml files containing tab contents.
Some of this work can be avoided by using session caching but some is not, mainly security checks.


----------------------------------------
> From: jackalmage at gmail.com
> Date: Sun, 18 Oct 2009 11:35:11 -0500
> Subject: Re: [whatwg] 
> To: t_garsiel at hotmail.com
> CC: derernst at gmx.ch; simetrical+w3c at gmail.com; whatwg at whatwg.org
>
> On Sun, Oct 18, 2009 at 11:22 AM, tali garsiel  wrote:
>> When I said an optimization is a must I didn't just mean bandwidth.
>> Imagine this use case:
>> You have a page with a chart and a table showing data calculated from complex statistical analysis on your huge database.
>> Both the chart and the table have "refresh" buttons implemented with "".
>> Recalculating the chart when you refresh the table or vice verse will not be acceptable by your project manager :)
>> The server will need to know what is currently requested.
>> The solution is not necessarily to strip the content, but the server must get information of the updated parts and choose what to calculate.
>
> That's not really an appropriate use of @onlyreplace. Just put the
> chart and table in s with @name and use <a target> to refresh<br />> them. That also automatically optimizes bandwidth, since the subpages<br />> that the chart and frame will live on contain *only* them.<br />><br />> (Preventing this sort of abuse might be a good reason to do the "only<br />> <base> can carry an id list" revision.)<br />><br />> ~TJ<br /> 		 	   		  
_________________________________________________________________
Keep your friends updated—even when you’re not signed in.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010