Refactor CORE-183
1 vote

Abstract ISparqlHttpProtocolProcessor so that it does not depend directly on HttpContext

Created by Rob Vesse on 2/17/2012 6:59 PM Last Updated by Rob Vesse on 5/31/2012 7:56 PM
%
 (hrs)
Logged: 0  (hrs)

 Description

Currently ISparqlHttpProtocolProcessor is directly dependent on HttpContext which means it is closely tied to that and so can't be used in a more general sense, for example within rdfServer currently which has a different web server model

 

The proposed refactor is to introduce an abstraction layer between the actual context and the context passed to the interface so that different web servers can be plugged into the system

    Rob Vesse (Wednesday, May 30, 2012 1:12 AM) #

Bulk of the work is done in revision 2215