Re: pageable recordsets broken

Yes, its was posted to the list, however, I will append it to the end  
of this email as well.  This modification works great and allows us  
to use the Flash Application in the Stand Alone Player

Regards


On Aug 14, 2005, at 4:51 PM, Sean C. Sullivan wrote:

>
> What did you change in the DefaultGateway?   Can you share your
> modification?
>
> Sean
>
>
> Will Prater wrote:
>
>
>> Yes I am.  I also had to edit DefaultGateway to keep the sessions
>> persistent, otherwise PageableRecords did not work at all.
>>
>> Thanks
>>
>>
>> On Aug 14, 2005, at 4:26 PM, Sean C. Sullivan wrote:
>>
>>
>>>
>>> Which version of OpenAMF?
>>>
>>> Are you using OpenAMF 1.0RC11?
>>>
>>> Will Prater wrote:
>>>
>>>
>>>
>>>> List,
>>>>
>>>> The current implementation of Pageable RecordsSets is broken.  The
>>>> server continually sends back the same RecordSetID.  When switching
>>>> from different RecordSets to page through you will end up getting
>>>> records from the previously paged Record.  We need to change the
>>>> RecordSetID with each new service call.
>>>>
>>>> Any ideas?
>>>>
>>>>
>>
>>
>
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle  
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams *  
> Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/ 
> bsce5sf
> _______________________________________________
> Openamf-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openamf-user
>



Begin forwarded message:

> From: Will Prater <[email protected]>
> Date: July 12, 2005 2:11:17 PM PDT
> To: [email protected]
> Subject: [Openamf-user] DefaultGateway path to automatically pass  
> session in URL from Flash
> Reply-To: [email protected]
>
>
> List,
>
> Here is a patch to automatically have Flash the session in the URL  
> when cookies are not available.  Please test this on Revisions 1.65  
> and let me know if you have any troubles.
>
> We are extending DefaultGateway and we did not use this conditional:
> >             if (!req.isRequestedSessionIdFromCookie()) {
>
> Im not certain that will work so if someone has better knowlege of  
> Java's SESSION implementation they would be better suited to first  
> find if the client was able to accept cookies.  If not then you  
> would add this header with each request.
>
>
> Thanks
>
>
> 197a198,207
> >             String sessId = req.getSession().getId();
> >             if (!req.isRequestedSessionIdFromCookie()) {
> >                 String newUrl = req.getRequestURL()
> >                     + ";jsessionid=" + sessId;
> >                 AMFHeader gatewayHeader = new AMFHeader(
> >                     "ReplaceGatewayUrl",
> >                     true,
> >                     newUrl);
> >                 responseMessage.addHeader(gatewayHeader);
> >             }
>
>
>

>
>
> -WP3

197a198,207
> 			String sessId = req.getSession().getId();
> 			if (!req.isRequestedSessionIdFromCookie()) {
> 				String newUrl = req.getRequestURL() 
> 					+ ";jsessionid=" + sessId;
> 				AMFHeader gatewayHeader = new AMFHeader(
> 					"ReplaceGatewayUrl", 
> 					true, 
> 					newUrl);
> 				responseMessage.addHeader(gatewayHeader);
> 			}