[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [wsrp][interfaces]: Operational questions to discuss
Please:
In the coming week I will update the document with the additional sections/questions
relating to portlet instances.
-Mike-
The portal has no knowledge that a portlet service exists.
No communication/operations to define.
Portal acquires meta data from portlet service:We have identified the following as function that should be possible during registration, are there others, do we need all of these (in our initial specification)? establish the portal vendors identify -- so the portlet can make adjustments to run in venders portal establish the portals identify -- so the portlet can distinguish between it and another portal it is servicing. establish a trust relationship with the portal (that can be maintained on susequent calls) -- so the portlet can control the level of security it requires. initialize themselves to be able to service this portal complete a subscription process communicate the set of portal services available to the portlet to plug into. (Examples include, logging service, monitoring service, personalization repository service, etc.) What information needs to be sent to establish a portal vendors identity? What information needs to be sent to establish a portal's identity? What are the levels of trust that can be established/maintained? How are each level established/maintained? What kinds of initialization do we envision a service doing when a new portal is registered? What information will it need from the portal to be able to do these initializations? What information needs to be supplied by the portal to complete a subscription process? How does a portal know it needs this information and ultimately get this information (particularly when the service is located using a standard directory service)? What information needs to be passed for a portal to make a portlet service aware of its services? Are there specific services we need to define as common to all portals? If so what are they? How does a vendor/portal pass non-standard information during registration so "aware" portals can have extended behaviors? Does the portal need to be able to perform registration over a secure channel? If so how does a portal know/discover that it needs to do this? What technologies must it be prepared to use to communicate securely? What information (if any) does the portlet service return to the portal on successful completion of registration? What information (if any) does the protlet service return to the portal on unsuccessful completion of registration? Note: this question may merely be asking what are the error states/codes we want to identify can be returned. Should a portlet service notify the portal that its been "upgraded"? I.e. that some information communicated via the registration phase has changed (most likely meta data) -- or if a service represents multiple portlets, the addition of new portlets managed by the service. If so how is this communicated? If it involves the portlet calling the portal what information does the portlet service receive and how does the portlet receive it in order to learn where/how to communicate back to the portal? Is this just another service type a portal can pass during registration? I.e. a portlet invalidation service? or jsut an event sent to the portal? Should a portlet service be able to notify the portal that being disabled/enabled (i.e. the portal will [temporaily] be unable to communicate with it? If it involves the portlet calling the portal what information does the portlet service receive and how does the portlet receive it in order to learn where/how to communicate back to the portal? Is this just another service type a portal can pass during registration? I.e. a portlet "disabled" service? or is it just an event sent to the portal?
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC