Implementing a WSRP producer - Portal based vs. Non portal based content

[John Menke <jo...@eagleinfosystems.com>]

The WSRP spec states that you can use WSRP to aggregate content via both
portlet and NON PORTLET producers.

QUESTION:

In order to implement a WSRP producer that is not connected to an actual
Portlet Container - not serving an actual 168 portlet.  It appears that i
will have to develop some type of service that mocks the 168 implementation
so that i can serve content to the consumer and provide the hooks into 168
that the WSRP spec seems to need.

For example the consumer request edit mode.  I will need my producer to
understand what edit mode means and stream back the edit mode content is
this correct?

The reason i am asking this question is that we are trying to determine if
we need create Portlets to serve content WSRP.  If we need to implement all
the 168 compliant features in a wrapper service in order to use WSRP is
seems like we would be reinventing the wheel by choosing not to create our
content as actual 168 portlets -- is this correct?

Is there any advantage in not creating 168 portlets and then serving them up
via a producer? ie just creating a producer?  Is this even possible?

thanks for any help,

jm