In todays IRC meeting I was asked to review the GSIPs (something I have not had time to catch up on).
(To start with the target is GeoServer 1.6, we may wish to consider the proposal and then schedule it according to risk/reward.)
Justin can we have a class diagram or sample code showing how the "Adapting Existing Services" will work? In particular I am wanting to see how (or if) GetCapabilities version negotiation will be handled. As I understand it this functionality was not needed for the wfs 1.1 branch.
So I agree with the motivations, and would like to establish the scope of work. Something in terms of an integration plan, even if it does not have dates in it would be great. I hope to see the complete picture in terms of cite tests and a milestone release.
In todays IRC meeting I was asked to review the GSIPs (something I have not had time to catch up on).
(To start with the target is GeoServer 1.6, we may wish to consider the proposal and then schedule it according to risk/reward.)
Justin can we have a class diagram or sample code showing how the "Adapting Existing Services" will work? In particular I am wanting to see how (or if) GetCapabilities version negotiation will be handled. As I understand it this functionality was not needed for the wfs 1.1 branch.
A class diagram is a good idea. Not sure what you mean about version negotiation? The dispatcher does do version negotiation. However since there are only single versions of wms and wcs it wont really matter to them.
So I agree with the motivations, and would like to establish the scope of work. Something in terms of an integration plan, even if it does not have dates in it would be great. I hope to see the complete picture in terms of cite tests and a milestone release.
In todays IRC meeting I was asked to review the GSIPs (something I have not had time to catch up on).
(To start with the target is GeoServer 1.6, we may wish to consider the proposal and then schedule it according to risk/reward.)
Justin can we have a class diagram or sample code showing how the "Adapting Existing Services" will work? In particular I am wanting to see how (or if) GetCapabilities version negotiation will be handled. As I understand it this functionality was not needed for the wfs 1.1 branch.
A class diagram is a good idea. Not sure what you mean about version negotiation? The dispatcher does do version negotiation. However since there are only single versions of wms and wcs it wont really matter to them.
I want to make sure that the dispatcher does in fact do version negotiation (when we went through code I did not see this); I would like to ensure that this functionality is included in the plan (or accounted for if you have already done it).
Right now the dispatcher does half and the job, and there is some logic in teh actual WFS GetCapabilities which does the other half.
Yes I would like to move it out and have all of it done by the dispatcher. There are some issues with this, but is something i have been meaning to do.
Jody Garnett wrote:
Justin Deoliveira wrote:
Jody Garnett wrote:
In todays IRC meeting I was asked to review the GSIPs (something I have not had time to catch up on).
(To start with the target is GeoServer 1.6, we may wish to consider the proposal and then schedule it according to risk/reward.)
Justin can we have a class diagram or sample code showing how the "Adapting Existing Services" will work? In particular I am wanting to see how (or if) GetCapabilities version negotiation will be handled. As I understand it this functionality was not needed for the wfs 1.1 branch.
A class diagram is a good idea. Not sure what you mean about version negotiation? The dispatcher does do version negotiation. However since there are only single versions of wms and wcs it wont really matter to them.
I want to make sure that the dispatcher does in fact do version negotiation (when we went through code I did not see this); I would like to ensure that this functionality is included in the plan (or accounted for if you have already done it).