Re: [vote] Portlet API - Compromise (Refinement)

2001-02-20 Thread Raphaël Luta
Santiago Gala wrote: ingo schuster wrote: At 20:04 02/16/01, Raphal Luta wrote: What would be the ideal time for an IRC chat ? Personnally I'd prefer either between 12:00 and 130:00 GMT (but I guess it's a bit early for the PST people out there) or near 19:00 - 20:00 GMT.

Re: [vote] Portlet API - Compromise (Refinement)

2001-02-19 Thread ingo schuster
At 20:04 02/16/01, Raphal Luta wrote: What would be the ideal time for an IRC chat ? Personnally I'd prefer either between 12:00 and 130:00 GMT (but I guess it's a bit early for the PST people out there) or near 19:00 - 20:00 GMT. Both times are ok with me. Did we already fix the day (Mo or

Re: [vote] Portlet API - Compromise (Refinement)

2001-02-19 Thread Santiago Gala
ingo schuster wrote: At 20:04 02/16/01, Raphal Luta wrote: What would be the ideal time for an IRC chat ? Personnally I'd prefer either between 12:00 and 130:00 GMT (but I guess it's a bit early for the PST people out there) or near 19:00 - 20:00 GMT. Both times are ok with me.

Re: [vote] Portlet API - Compromise (Refinement)

2001-02-18 Thread ingo schuster
At 20:04 02/16/01, Raphal Luta wrote: I updated the java docs in the proposals directory so that everybody can have a look at them. They are more detailed, but I hope that this mail did also make the idea clear. I still owe you a proposal that defines which rules document fragments will have

Re: [vote] Portlet API - Compromise (Refinement)

2001-02-16 Thread ingo schuster
I haven't had much feedback on the proposed compromise but after a private discussion with Raphal I think that some more detailed description will be helpful. Furthermore, even though my proposal allowed to use both approaches (portlets delivering output streams to the container as well as

Re: [vote] Portlet API - Compromise (Refinement)

2001-02-16 Thread Raphaël Luta
At 14:33 16/02/2001 +0100, you wrote: I haven't had much feedback on the proposed compromise but after a private discussion with Raphal I think that some more detailed description will be helpful. Furthermore, even though my proposal allowed to use both approaches (portlets delivering output

RE: [vote] Portlet API - Compromise

2001-02-15 Thread David Sean Taylor
I'd like to applaud Ingo for stepping up and trying to find a middle ground. Impressive ascii-diagram too :) SaxPortlet has specific knowledge about the portlet container's implementation of the response. Now the portlet container's ResponseImpl can provide additional methods such as

RE: [vote] Portlet API - Compromise

2001-02-15 Thread ingo schuster
At 08:11 02/15/01, David Sean Taylor wrote: I'd like to applaud Ingo for stepping up and trying to find a middle ground. Impressive ascii-diagram too :) SaxPortlet has specific knowledge about the portlet container's implementation of the response. Now the portlet container's ResponseImpl

RE: [vote] Portlet API - Compromise

2001-02-15 Thread David Sean Taylor
Not really. If you want to process sax events in the portal engine, then it doesn't make sense to convert it into a stream in the SaxPortlet and reparse it on the other side of the portlet in order to convert it back into sax events. I wasn't suggesting that! Guess I misunderstood the

Re: [vote] Portlet API - Compromise

2001-02-14 Thread ingo schuster
Hi, I'm meanwhile convinced, that this discussion won't lead to a consensus, if each of us keeps defending his view on a technical level. However, I really like to find a compromise that everybody can agree on. On a meta level of this discussion, I can see the point that it would hurt the