On Mon, Jan 7, 2013 at 5:19 PM, Justin Deoliveira <[email protected]>wrote:
> Yeah, I didn't like LayerableInfo. I thought about PublishedInfo as well
> since more or less what they share is all the "publishing" metadata . I do
> kind of like it since it would be a separation of those entities (like
> layer and layer group) which represent the published aspect from those that
> are sort of internal entities (resource, store, etc...)I guess the question
> is how likely is it that something else might want to extend this same
> interface, ie share this same publishing metadata.
>
Likely, in the short term... uh, I guess not very much?
What else could be publisheable as a layer of sorts? Maybe map decorations
of some sort?
Another thing that could sooner or later come in is the idea of having a
WPS process be a source of data
for a layer, but I guess in that cause we'd make the WPS process a resource
too, so that it can be used
from WFS and WCS too
Cheers
Andrea
--
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
