User1
Azure SingalR (WebSocket) MessagingQueue Topic (serviceBus)
WebAPI (RestfulAPI) Database, NoSQL (Cosmosdb)
User2 Caching server( RedisCache )
Box(image/video)
enum elevatorStatus{Moving,Idle,Stopped}
enum elevatorDirection{Up,Down}
elevator
{
currentflor
Status -moving ,idle stopped
CurrentDirection- up down
}
sortedlist CurrentDirectionList
SortedList OtherPressUp
SortedList OtherPressDown
ExternalRequest
{
floor
direction
}
InternalRequest
{
floor
direction
}
- addToProcessingFloor(ExternalRequest) //SomeonePressingButton from outside
-switch{
case Idle:
CurrentDirectionList.Add()
case Moving:
if(Up)
//up
ExternalRequest.Up
if(currentfloor<ExternalRequest.floor)
CurrentDirectionList.Add()
else AddTO OtherPressUp
else //down
ExternalRequest.Down
if(currentfloor>ExternalRequest.floor)
CurrentDirectionList.Add()
else OtherPressDown
case Stopped:
CurrentDirectionList.Add()
}
- WhenIdel()
case Moving:
if(Up)
//up
CurrentDirectionList= OtherPressDown
CurrentDirection =down
else //down
CurrentDirectionList= OtherPressDown
CurrentDirection =down
-addToProcessingFloor(InternalRequest)//Somepress button side
-switch{
case Idle:
CurrentDirectionList.Add()
case Moving:
if(Up)
//up
if(currentfloor<InternalRequest.floor)
CurrentDirectionList.Add()
else AddTO OtherPressDown
else //down
if(currentfloor<InternalRequest.floor)
CurrentDirectionList.Add()
else OtherPressUP
case Stopped:
CurrentDirectionList.Add()
}
dotnet publish -c Release
FROM microsoft/aspnetcore
WORKDIR /app
COPY . .
CMD ASPNETCORE_URLS=http://*:$PORT dotnet <AssemblyName>.dll
Be sure to replace <AssemblyName> with the name of your project assembly e.g. SampleWebApi
./bin/release/netcoreapp2.0/publish
docker build -t <image-name> ./bin/release/netcoreapp2.0/publish
Be sure to replace <image-name> with the name you intend to give the image e.g. sample-web-api
heroku login heroku container:login
docker tag <image-name> registry.heroku.com/<heroku-app-name>/web
docker push registry.heroku.com/<heroku-app-name>/web
Be sure to replace <heroku-app-name> with the name of your heroku app e.g. sample-web-api
heroku container:release web --app <webappName/imagename>Access-Control-Allow-Originresponse header to tell the browser that the content of this page is accessible to certain origins. (Anorigin is a domain, plus a scheme and port number.) By default, Site B's pages are not accessible to any other origin; using the Access-Control-Allow-Origin header opens a door for cross-origin access by specific requesting origins.Access-Control-Allow-Origin: http://siteA.comXMLHttpRequest's error event and deny the response data to the requesting JavaScript code.AcceptAccept-LanguageContent-LanguageContent-Type (this is only simple when its value is application/x-www-form-urlencoded, multipart/form-data, or text/plain)Access-Control-Allow-Headers for non-simple headers, Access-Control-Allow-Methods for non-simple verbs) that match the non-simple verb and/or non-simple headers, then the browser sends the actual request./somePage, with a non-simple Content-Typevalue of application/json, the browser would first send a preflight request:OPTIONS /somePage HTTP/1.1
Origin: http://siteA.com
Access-Control-Request-Method: PUT
Access-Control-Request-Headers: Content-TypeAccess-Control-Request-Method and Access-Control-Request-Headers are added by the browser automatically; you do not need to add them. This OPTIONS preflight gets the successful response headers:Access-Control-Allow-Origin: http://siteA.com
Access-Control-Allow-Methods: GET, POST, PUT
Access-Control-Allow-Headers: Content-TypeAccess-Control-Allow-Origin again for the actual response).PUT /somePage HTTP/1.1
Origin: http://siteA.com
Content-Type: application/json
{ "myRequestContent": "JSON is so great" }Access-Control-Allow-Origin, just as it would for a simple request:Access-Control-Allow-Origin: http://siteA.com |
| fig 1 |
 |
| fig 2 |
 |
| fig 3 |
 |
| fig 4 |
 |
| fig 5 |
 |
| fig 6 |