Raphaël Luta wrote:
> Todd Kuebler wrote:
>
>> Ok, finally had a chance to dig around in the Capability Map stuff in
>> both jetspeed and the portal API areas.
>>
>> I definately agree that the capability map direction is the one to go
>> to add the features contained in my proposal.
>>
>> I ha
Todd Kuebler wrote:
> Ok, finally had a chance to dig around in the Capability Map stuff in
> both jetspeed and the portal API areas.
>
> I definately agree that the capability map direction is the one to go to
> add the features contained in my proposal.
>
> I have a few questions:
>
> 1) If
Ok, finally had a chance to dig around in the Capability Map stuff in both
jetspeed and the portal API areas.
I definately agree that the capability map direction is the one to go to
add the features contained in my proposal.
I have a few questions:
1) If I read the code right, no changes to
;Would you like to sign up for the documentation tasks for the '1.4
>beta'? ;) ;)
>
>David
>
>
>
>
>>-Original Message-
>>From: [EMAIL PROTECTED]
>>[mailto:[EMAIL PROTECTED]]
>>Sent: Thursday, May 23, 2002 10:30 AM
>>To: Jet
At 10:08 AM 5/23/2002 +0200, you wrote:
>Todd Kuebler wrote:
>
>Defintions:
>* client: a client is a software used to access the portal content. A client
> is identified by a user-agent string and supports one or several
> content type
> as well as one or several capabilities.
>* content type
gt; From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 23, 2002 10:30 AM
> To: Jetspeed Developers List
> Subject: Re: Proposal: Template Locator search path includes
> browser type
>
>
> David Sean Taylor wrote:
> >>Sorry to jump late on thi
Thanks for all the feedback, I figured you guys might have some better ideas.
Using the capability map seems to be the consensus. Let me introduce
myself to the idea of extending the capability map portion of the code and
chew on this for a day or so before I agree it's best (sure it is, just
David Sean Taylor wrote:
>>Sorry to jump late on this, but I'm -1 for this as this is
>>Jetspeed is already architected to be able to handle this
>>(although the implementation is incomplete right now).
>>
>
> Raphael,
>
> Would you consider changing your vote if Todd implements it the way you
The proposal, specifically adding directories to the path, MUST be
amended to include updating JetspeedLink, the ProfileLocator, the PSML
database, and any other components of Jetspeed that need to know the
path or use the path to the PSML. Otherwise, I will not support this
proposal.
Paul S
> Sorry to jump late on this, but I'm -1 for this as this is
> Jetspeed is already architected to be able to handle this
> (although the implementation is incomplete right now).
>
Raphael,
Would you consider changing your vote if Todd implements it the way you
suggested?
David
--
To unsubs
Todd,
In many ways this should be handled by the capability map.
***
*** Default behavior of the capability map:
***
The capability map's need the ability to handle is a "default media
type" for a media type. Using the directory structure below. A request
from a Netscape 4.7 borrower, or a wa
Todd Kuebler wrote:
>
> I propose we change the search path of the jetspeed template locator
> service to include browser directories. The changes will be made to the
> current JetspeedTemplateLocatorService.
>
> The search path algorithm would be the same as now, with the addition of
> the
Hi,
--- Todd Kuebler <[EMAIL PROTECTED]> wrote:
>
> I propose we change the search path of the jetspeed template
> locator
> service to include browser directories. The changes will be made
> to the
> current JetspeedTemplateLocatorService.
>
[snip]
> templates/vm/layouts/html/en/default.v
--
> From: Todd Kuebler [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 22, 2002 4:29 PM
> To: Jetspeed Developers List; 'Jetspeed Developers List'
> Subject: Proposal: Template Locator search path includes browser type
>
>
>
> I propose we change the search pa
I propose we change the search path of the jetspeed template locator
service to include browser directories. The changes will be made to the
current JetspeedTemplateLocatorService.
The search path algorithm would be the same as now, with the addition of
the browser directory if there is at l
15 matches
Mail list logo
