[Ovirt-devel] [PATCH] fixed some 500 internal server errors

[Hugh O. Brock]

On Mon, Jun 02, 2008 at 01:33:30PM -0400, Jason Guiditta wrote:
> Hugh O. Brock wrote:
>> [snip]
>> ACK, this appears to work fine. I have committed and pushed it along
>> with the other three that preceded it.
>>
>> Is it easy, or worth doing, to include a check so that the content
>> pane does not reload if the user clicks its link in the tree again? Or
>> do we *want* it to reload?
>>
>> Take care,
>> --Hugh
>>   
>
> With the current implementation (that I hope we are cleaning up after 
> summit), this would take a bit of work, but could be done.  However, unless 
> we are going to stream data to the browser for everything in that content 
> pane (comet or periodic updates), I would think we would want it to refresh 
> when you click the link again, if only for a simple mechanism to update the 
> content in that pane.  This is starting to get to a point where we need 
> some cohesive decisions made on how we want the app to behave.  If there 
> will be no refresh on click of the pool for the associated content, then we 
> _have_ to be updating everything in the content area (all tabs, since you 
> could have chosen any).  I _really_ would not want to see this done with 
> polling - it is bad enough as a temporary way for updating the tree (what I 
> am working on now), to have it everywhere would be a horrible amount of 
> chattiness to the server.

Yeah, that makes sense; I don't feel all that strongly about it
anyway.

Thanks,
--Hugh