[PYTHON] Let's make a spot sale service 9 (Task Queue edition)

Field map

I can finally make a field map, but I will decide this time because the details of the interaction between the server and the client have not been decided yet.

To see this screenshot What the client wants

• Please map information

On the other hand, the server

• This venue is the size of (w, h)

• There is a xxx circle in the square (a, b)

• There is a yyy circle in the square (c, d)

• There is a zzz circle in the square (e, f)

• There is no circle in the square (g, h) (only there is a desk)

  : :

Circle information is quite so if you know the circle id and the url of the circle cut. If you manage the squares in one dimension, it will be easier to handle. Characters walking around the venue will randomly walk like the villagers of Dragon Quest.

About the logic that decides where to place the circle

The location is decided at the moment when the store is opened from the circle menu. At present, we will decide the candidates in advance and randomly acquire them.

The place to place it is where you painted red and black with the following squares.

When a circle opens a store, it seems good to create it in advance with 1 store opening location / 1 entity in the Data Store and search for locations that have not yet opened.

It is a method to create in advance, but hard-code as follows. https://gist.github.com/nagai/3788f27b94d5321abb7f Since the amount of writing of the entity was large and it seemed to take time to create the circle space Parallelized using TaskQueue. Also, since this api is not needed by anyone other than the service administrator,

app.yam

- url: /admin/api/event/.*
  login: admin
  secure: always
  script: controller.admin.api.event.app

And login is required with administrator privileges.

That's why today's brunch is here https://github.com/nagai/freemarket/tree/20140511

Next time, we will create circle entry / exit processing and field map rendering on the client side.