When you download and open WOFpy, you can find the following folders
As mentioned earlier, WOFpy can be compared to a restaurant. The components of WOFpy can be compared to the following members of the catering staff:
Web services are what the data consumer interact with. WOFpy provides both REST (REpresentational State Transfer) and SOAP (Simple Object Access Protocol) web services. These web services are designed to handle the four main WaterOneFlow methods: GetSites, GetVariables, GetSiteInfo and GetValues.
WOF is the core package within WOFpy. Processes web service requests Uses DAOs to acquire data from native database Assembles WaterML objects into WaterML and returns them Contains SOAP and REST web service classes and URL templates
Organized the way you want to organize it.
DAO = Data Access Packages Contains Object Relational Mapping (ORM) to map from native database schema to WaterML objects. Customized by data provider
Determines which native database(s) to publish Determines which DAO(s) to use Starts the WOFpy web services
From the viewpoint of the code, the following diagram shows the location of the different components within WOFpy’s file structure.
When you download and open WOFpy. You will notice that it contains the following file structure.
(Only selected folders are expanded).
WOFPY| readme.txt | setup.py | +—docs| +—examples| +—barebones| +—cbi| +—odm_sqlserver| —swis| +—test| —wof
+—flask| | config.py | | __init__.py | | | +—templates| | index.html | | wml2_values_template.xml | | wsdl_temp.wsdl | | | —views| rest.py | wsdl.py | __init__.py | —soapsoap.py __init__.py
WOFpy contains 4 main
(to be linked to epydoc files in /_build/html/epydoc/)