Ugh.. Well, it was worth a shot. :) On Tuesday, February 4, 2014 8:42:00 PM UTC-5, Jeff Hubbard wrote: > > Every version of IE that I am aware of--certainly IE6 thru 10--has the > 2083 character limit on the full URL, just FYI. > > On Tuesday, February 4, 2014 4:07:52 PM UTC-8, Erez Lirov wrote: >> >> What about encoding the fields as a base-64-encoded json object that you >> can append to your search URL? This way, filling fields will cause a new >> URL to be generated that will encode the field values. The URLs will be >> long, but I'm not sure that would be an issue unless you need to support >> IE6. >> If you generate a base-64 URL, you'll need to encode it to deal with +, >> =, and /. (maybe using replace()) >> >> On Tuesday, February 4, 2014 12:10:13 PM UTC-5, Andrew Ketner wrote: >>> >>> Here is the basic problem. In a single page angular application. Say >>> you have a page withe 60 fields of text boxes, combo boxes, radio buttons, >>> and check boxes to narrow your search parameters. You enter your >>> criteria, click search. You get a data grid of data. You choose one of >>> the items in your grid, That takes you to the detail page. You realize >>> that's the wrong dude so you click the back button. What happens in >>> angular is when you get to the previous page, all the data you entered is >>> gone and it's back to default, you have to renter all your criteria. >>> >>> Now angular has a deep link tracking system built into its routing >>> system that will put all of those parameters into the URL, but the problem >>> is we have search pages with so many fields that it's impractical to put >>> them into the URL like that. What we really need is an old school view >>> state system similar to what we had to build in the days of php and asp, >>> >>> I need some way to capture the view state and save it off to the server >>> in either a cache or a redis server, It has to be server side because the >>> amount of data is too big for cookies and the users will actually be >>> jumping outside the angular app, into the legacy struts app, and then back >>> buttoning back into the angular app. When the user back buttons back into >>> the angular app, the thing has to go back to the server, get the view state >>> object, and rebuild the view state to restore where the user was when they >>> left. >>> >>> >>> ANY HELP OR IDEAS WOULD BE GREATLY APPRECIATED >>> >>>
-- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
