Re: SLD SERVICE RESTLET PROPOSAL!

> Hi Andrea,
> first of all, sorry for the very very late answer.
>

 Hi Andrea,
 I have to apologize too for my very very very late answer.

>    I'd suggest to stop the splitting at the rule level, and
>    to allow full download on the upper levels by using a parameter
>    (for example, &content=full)

I agree, but I think is better to avoid the use of parameters in restlet
We can find a different url mapping this request. Maybe we can return
all the content rules excluded at
-> http://domain:8080/geoserver/sldservice/{featureType}/{UserStyleID}



> * the idea of having services generate resources server side
>    seems fine, thought the url does not look right to me. Given
>    that you're calling an algorithm, the url should be something
>    like:
> http://domain:8080/geoserver/sldservice/{featureType}/{UserStyleID}/{FeatureTypeStyleID}?quantileclassification&property={property}&classNum={num}
>    I'm also not sure about the type of method, but since it's
>    creating resources I guess it should be a POST
 As before, I'm not a great expert of Rest but I think that in a Rest
architecture we have to avoid the use of parameters, but I'm not sure. :-)



 * the split does work well on the read side, but seems to
>    fall on the write side. When you create an SLD server side
>    it must be valid, not an incomplete document.
     is an SLD domcunmet without any rule a valide one?

 Thanks for your comments
kappu

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@...
https://lists.sourceforge.net/lists/listinfo/geoserver-devel