Carlos Araya wrote:
>Whoever starts the thread may, once a week or so (depending on the thread's
>traffic), post a summary. That way the people who have been away can catch
>up to the discussion? Then you can put those summaries on an RSS channel.
Such a channel (Kernel Cousing cocoon-dev, anyone
no, you got it right. I sent it around 3am so I will claim that I was
operating with tired brain cells :(
error between keyboard and chair
thanks
- Original Message -
From: "MJ Ray" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, January 06, 2002 3:56 AM
Subject: Re: [Request]
If I may make a suggestion:
Whoever starts the thread may, once a week or so (depending on the thread's
traffic), post a summary. That way the people who have been away can catch
up to the discussion? Then you can put those summaries on an RSS channel.
On 01/06/02 3:44, "MJ Ray" <[EMAIL PROTECT
Robert Koberg wrote:
>What takes longer to come to boil in a microwave oven:
[...]
>0:01:11. This is because it is faster/easier for the user to hit the "1"
>button three times rather than for them to search for the "0".
I think you got that example backwards, or did I miss the point completely?
Gianugo Rabellino wrote:
>I challenge any of you to catch up after a few days away from the ML,
>get a message from a populated thread, glance at it and understand what
Oh yes, it's not easy, especially for people like me who only read the list
every few days. The only way this place is tolera
Stefano Mazzocchi wrote:
>Vadim Gritsenko wrote:
>
>>you have product catalog sub-sitemap:
>>
>>
>> ...
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ...
>>
>>Example might be not perfect, but it gives an idea...
>>
>
>Yeah, gives me the idea that the whole concept is screwed and can
>potentially
giacomo 02/01/06 09:18:26
Modified:src/scratchpad/src/org/apache/cocoon/jispstore
FilesystemQueueImpl.java JispFilesystemStore.java
JispStringKey.java MRUMemoryStore.java
Log:
fixed EOL encoding
Revision ChangesPath
1.3
John Morrison wrote:
>>Agreed. -1 as well. Well, until somebody comes up with the need for an
>>action to be executed *after* a serializer.
>>
>
>How about this one: if the serializer doesn't throw an exception then
>you *know(?)* the client recieved the request. An action after
>serialization m
froehlich02/01/06 06:28:10
Modified:src/scratchpad/src/org/apache/cocoon/jispstore
MRUMemoryStore.java JispStringKey.java
JispFilesystemStore.java FilesystemQueueImpl.java
Log:
removed odd "new line" format and changed store method tow
> The kinds of things I am referring to include (off the top of my head):
>
>- SoC (What does a concern look like? How much separation is enough?
Etc.
> )
>- The "proper" design of URLs (.../cocoon1 vs. .../cocoon/old vs. ...)
>
>
> People on this list do step in and say "this is mixing c
10 matches
Mail list logo