Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 37703

Summary:	[plan item] Provide working sets for help infocenter
Product:	[Eclipse Project] Platform	Reporter:	Jim des Rivieres <jeem>
Component:	User Assistance	Assignee:	Konrad Kolosowski <konradk>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	cameronk, ecsmyth, konradk
Version:	2.1	Keywords:	plan
Target Milestone:	3.0 M1
Hardware:	All
OS:	All
Whiteboard:

Description Jim des Rivieres

2003-05-15 11:28:41 EDT

Provide working sets for help infocenter. Persistent help working sets were 
added in Eclipse 2.1. This support is not available is infocenters, where the 
user must still rely on searches (which are not persisted). Persistent working 
set support should be added to infocenters as well. [Platform Help]

Comment 1 Konrad Kolosowski

2003-05-26 23:56:36 EDT

*** Bug 37450 has been marked as a duplicate of this bug. ***

Comment 2 Konrad Kolosowski

2003-05-28 12:49:28 EDT

The issue with working set was with persisting data for multiple users of the 
infocenter.

I have released code for supporting working set in the infocenter.  Added 
InfocenterWorkingSet manager class to manage working sets per client.

The data is persisted in cookies that are set by the server and sent to the 
client.  This way no data is stored on the server and we avoided the need for 
user accounts that would be needed for identyfing users for the purpose of 
retrieving data stored on the server.  

Multiple cookies are used if necessary, when data does not fit into one when 
many books or topic are selected or user defines large number of working 
sets.  There is 4kB cookie size limit.  We set maximum of 15 cookies to be 
used for storing working set information, as the specs allow 20 cookies max 
per site.

Done.

Comment 3 Konrad Kolosowski

2004-10-19 09:14:22 EDT

*** Bug 76493 has been marked as a duplicate of this bug. ***

Comment 4 Konrad Kolosowski

2005-01-11 10:14:24 EST

*** Bug 82535 has been marked as a duplicate of this bug. ***