it seems that in this case, the query string was the good option. i've converted the POST into GET and it solved all my problems.
and here it started to rain :)) On Aug 6, 5:17 pm, Ken Egozi <[email protected]> wrote: > if the whole filter is in the query string - think of what your user can > acheive - bookmarkabilitythat is - you gain a "saved search" capability, by > simply telling the user to bookmark the url with the filter. > > plus the user can send the url to a friend > > > > On Thu, Aug 6, 2009 at 5:13 PM, bdaniel7 <[email protected]> wrote: > > > One reason for which i don't like query string, for this instance, is > > that there are 11 fields usable in filter and the query string can get > > quite long. > > But i suppose i can use this, in lack of other choices. > > > On Aug 6, 4:50 pm, Ken Egozi <[email protected]> wrote: > > > an html form with method="get" will serialize it's values (the ones with > > > name atttribute) to the query string.The most obvious example > > > (which reassembles your situation) is google's search box. > > > > On Thu, Aug 6, 2009 at 4:48 PM, bdaniel7 <[email protected]> wrote: > > > > > On Aug 6, 4:47 pm, bdaniel7 <[email protected]> wrote: > > > > > I don't think is possible to send values to server using a GET. > > > > > So how can i submit the form trough GET? > > > > > Except for query string, of course. > > > > > > On Aug 6, 4:22 pm, Simon Laroche <[email protected]> wrote: > > > > > > > Why not submit the form through GET and include the current page in > > the > > > > form? > > > > > > > Simon > > > > > > > On Thursday, August 6, 2009, bdaniel7 <[email protected]> wrote: > > > > > > > > Hello, > > > > > > > I ran into an annoying issue: > > > > > > > > I have a list of items, paged which is working properly. > > > > > > > The customer wants also to filter the data by several criteria. > > > > > > > The filtering is done by sending through POST a form with several > > > > > > > criteria and their values. > > > > > > > > Now it comes the problem: > > > > > > > the paging is done with querystring, using GET. > > > > > > > the filtered data set must also be paged, but it doesn't work > > because > > > > > > > the filter can be used only with a POST. > > > > > > > > after much trial and error, i thought of 2 solutions: > > > > > > > 1. send the filter params and values though querystring (as I've > > seen > > > > > > > in some examples) > > > > > > > 2. cache the data, after it was retrieved so that the list/filter > > > > > > > action can retrieve it and use it no matter if by POST of GET. > > > > > > > > I prefer option 2 because is much clean. > > > > > > > and i can use something already in Castle to achieve it. > > > > > > > > Any other suggestions? > > > > > > > > Thank you, > > > > > > > Dan > > > > -- > > > Ken Egozi. > >http://www.kenegozi.com/bloghttp://www.delver.comhttp://www.musicglue... > > -- > Ken > Egozi.http://www.kenegozi.com/bloghttp://www.delver.comhttp://www.musicglue.comhttp://www.castleproject.orghttp://www.gotfriends.co.il --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
