Good News Everybody!
The new search engine is LIVE!
Please report any problems to david (at) midrange.com.
|
Hi Everyone,
I just recently jumped in to the realm of using IWS to provide RESTful
services. I am using the program to feed data to a web portal that
will show a grid of information in it for whatever customer has logged in.
Initially when loading the grid, it will be shown in date/time format
with most recent activity at the top. But, then I want to have the
ability to allow the user to perhaps filter the data or click a column
heading and sort the data. Full disclosure, I am not the user
interface guy on this, just the person providing the data back in a JSON format from IWS.
So, right now this works great:
http://myserver:10010/web/services/TICKETS/xxxxxxxxxx
Where "xxxxxxxxxx" is the customer ID and is set up as a *PATH_PARAM.
This would always be a required part of the path.
So a real URL might look like:
http://myserver:10010/web/services/TICKETS/CUSTOMERA
Now I am trying to figure out how to accept in additional parameters
in to the request that might be for sorting or filtering the data. I
think a real request might look like:
http://myserver:10010/web/services/TICKETS/CUSTOMERA?state=closed&sort
=-updated_at
This would retrieve tickets for customer A where the state is closed
and sort them with most recent at the top.
So, with all that said, how do I set up the service program to accept
this "?state=closed&sort=-updated_at" and how do I configure the IWS
service to accept it and pass it in?
I am thinking maybe the sort/filter is another entry parameter but
I've not been able to get it to work so I am hoping someone here has
already blazed this trail. There still does not seem to be a ton of
info out there on IWS and even less with IWS and RESTful services.
Thanks all in advance,
Brian
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.