[wsrp] writing producers

Carsten,

In response to the last sentence of your email.

Do you envision developers writing producers that implement the WSRP 
protocol as something common?

My take here is that most (if not all) developers will write portlet 
components a la Servlets (using different languages, frameworks, 
platforms) and these components will run in a container that provides 
the support for WSRP. The interfaces that we have are complicated enough 
for an average developer to code against.

If we agree that the existence of such container in the producer side 
will be the common case, then we also could assume that the producer 
(the container) will be able to handle more complexity while hiding it 
from the portlet developer.

Regards.

Alejandro.

Carsten Leue wrote:

>Rich - very good proposal. As already indicated in the discussions I would
>certainly vote for options #2. They put less burden on the producer, allow
>for static producer content and still allow for efficient processing on the
>consumer side (by applying fast string matching algorithms like the BM alg.
>and selecting the StartToken carefully). Let's keep in mind that we
>envision a world in which it is easy to write and producer and we (the
>portal vendors) write the consumers.
>
>
>Best regards
>Carsten Leue
>
>-------
>Dr. Carsten Leue
>Dept.8288, IBM Laboratory B鐽lingen , Germany
>Tel.: +49-7031-16-4603, Fax: +49-7031-16-4401
>  
>