Mailing-List: contact dev-help@click.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@click.apache.org
Received-SPF: pass (nike.apache.org: domain of
 gcwcd-click-development-2@m.gmane.org designates 80.91.229.12 as permitted
 sender)
To: dev@click.apache.org
From: "Adrian A." <a.adrian.tech@gmail.com>
Subject: Re: Rename Partial
Date: Sun, 18 Jul 2010 09:50:36 +0200
Lines: 37
Message-ID: <i1ubod$gq4$1@dough.gmane.org>
References: <4C4188D3.4080509@gmail.com> <i1s357$lm1$1@dough.gmane.org>
 <4C419540.5080003@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US;
 rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1
In-Reply-To: <4C419540.5080003@gmail.com>

>> Fragment, (Snippet, Slice, Brick, Pagelet, Partlet, Slicelet) ?
>>
>> The "binary" content returned, it's indeed "complete", not "partial",
>> but maybe the problem (and user confusion) is not with the naming, but
>> the fact that "Partial" renders non-Ajax binary content too? For those
>> binary resources, a much better name could be e.g. "Resource", so
>>
>> E.g. Something like
>> public class Partial extends/implements Resource {
>>   ...
>> }
>> thus for "complete" binary responses to return a Resource, not a Partial?
>>
>> Could this be an approach?
>
>
> Not sure that Resource is the proper name though. It might be binary
> content that is generated on the fly.
"Resource would be the "Browser"/"User" view on that generated content - 
being static or dynamic. The same way a HTML Page is the same from the 
Browser/User perspective even if it's dynamically created or not.

The same wording seem to be used by REST and RESTful web services (what 
comes back is a "resource")

> Both JSF and Wicket have settled on Behaviors so I think we should leverage it as well.
That was the first issue mentioned to me by some users: it's just too 
Wicket like :).

> Callbacks
> might be more familiar to programmers but not as a means to handle Ajax requests. Callbacks are
> normally used for inter object invocations not handling browser requests.
Something familiar to most Windows users (but present in many 
programming languages) might be "Handle" or "AjaxHandle".

Adrian.