Re: [Phrame-devel] ActionForward::AppendPath() method?

[Alex <ale...@ya...>]

> Adding it to the forward path _IS_ adding it to the
> request (for the next page
> view), right?

True.

> In this case, I do not want to have it be a session
> variable 

You wouldn't want that indeed. I'd have
gone with a request variable, but phrame 2
implements that like session if I am not
mistaken.

> for a couple of
> reasons:
> 1) if they want to bookmark editing a particular
> item, they can go back
> directly
> 2) if they use their history for navigation, they
> can return to editing a
> previous item

Good points. Go with your plan.

> If I adopted use of the session, they would be
> forced to alway go back through
> the overall item navigation to get to the particular
> item they want to edit. 
> Any holes in that logic?

I'd say:
"Back button considered evil"
but you are right.

About the AppendPath method,
perhaps we could add a bit more. We could 
make a method that just accepts a key/value
pair (or an array/hashmap of such) and 
append that to the path.

That way we don't have to worry about & and ? 
in the url, and perhaps it does some encoding 
of the data as well.

>
-------------------------------------------------------
> This SF.net email is sponsored by: ObjectStore.
> If flattening out C++ or Java code to make your
> application fit in a
> relational database is painful, don't do it! Check
> out ObjectStore.
> Now part of Progress Software.
> http://www.objectstore.net/sourceforge
> _______________________________________________
> Phrame-devel mailing list
> Phr...@li...
> https://lists.sourceforge.net/lists/listinfo/phrame-devel

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com