update,
7
eymko/gitUpdate.bat
Normal file
@@ -0,0 +1,7 @@
|
||||
git status .
|
||||
|
||||
@pause
|
||||
|
||||
git add .
|
||||
git commit -m"update eymko,"
|
||||
start git push
|
1
eymko/meta.md
Normal file
@@ -0,0 +1 @@
|
||||
eymko
|
BIN
eymko/task1-quote/1/WhatsApp Image 2024-06-18 at 2.33.54 PM.jpeg
Normal file
After Width: | Height: | Size: 366 KiB |
BIN
eymko/task1-quote/1/WhatsApp Image 2024-06-18 at 2.33.55 PM.jpeg
Normal file
After Width: | Height: | Size: 267 KiB |
BIN
eymko/task1-quote/1/screencapture-microbit-org-get-started-features-overview-2024-06-18-14_50_15.png
(Stored with Git LFS)
Normal file
After Width: | Height: | Size: 306 KiB |
BIN
eymko/task1-quote/2/screencapture-microbit-org-get-started-features-overview-2024-06-18-14_50_15.png
(Stored with Git LFS)
Normal file
After Width: | Height: | Size: 369 KiB |
After Width: | Height: | Size: 354 KiB |
5
eymko/task1-quote/4/ans.txt
Normal file
@@ -0,0 +1,5 @@
|
||||
something similar to:
|
||||
|
||||
https://www.youtube.com/watch?v=2aAcBP2xcaI
|
||||
|
||||
12:52
|
BIN
eymko/task1-quote/5/WhatsApp Image 2024-06-18 at 2.33.56 PM.jpeg
Normal file
After Width: | Height: | Size: 370 KiB |
BIN
eymko/task1-quote/6/Code_O205ZqdRop.png
(Stored with Git LFS)
Normal file
After Width: | Height: | Size: 474 KiB |
4
eymko/task1-quote/6/ans.txt
Normal file
@@ -0,0 +1,4 @@
|
||||
IR transmitter and IR receiver
|
||||
start
|
||||
end subtract
|
||||
display
|
BIN
eymko/task1-quote/7/WhatsApp Image 2024-06-18 at 2.33.58 PM.jpeg
Normal file
After Width: | Height: | Size: 365 KiB |
5
eymko/task1-quote/7/ans.txt
Normal file
@@ -0,0 +1,5 @@
|
||||
something similar to:
|
||||
|
||||
https://www.youtube.com/watch?v=2aAcBP2xcaI
|
||||
|
||||
8:46
|
After Width: | Height: | Size: 200 KiB |
7
eyt278181/gitUpdate.bat
Normal file
@@ -0,0 +1,7 @@
|
||||
git status .
|
||||
|
||||
@pause
|
||||
|
||||
git add .
|
||||
git commit -m"update eyt278181,"
|
||||
start git push
|
16
eyt278181/meta.md
Normal file
@@ -0,0 +1,16 @@
|
||||
monitor-24.com
|
||||
|
||||
明白嘅,
|
||||
咁我又假設有客人想做 integration ,
|
||||
咁我想再問下有冇機會有 API doc 呢類文件可以望一望?
|
||||
|
||||
唔好意思先,我可能未帶到客仔比你住,不過傾開我想了解多 D 先
|
||||
假設有客人買 1 lot (例如過千個 website monitor )咁先算啦
|
||||
咁一般而言都唔會叫個客人一個一個咁督入去架嘛
|
||||
咁所以好多時都有 D 叫 "API" 嘅野話比客仔可以點樣去 integrate 落去你地服務果度,咁果份 doc 就叫 "API doc".
|
||||
|
||||
Sorry in advance as i may not the right on to get customer to you but i would liek to know more by this chance.
|
||||
|
||||
so let say someone (possibly a corperate-customer) would like to subscribe one lot (let say 1000 website monitoring) service from you. how can you serve ? currently, AFAIK a popular model is leaving a API (endpoint) that can communiate with your system. when customer pass a HTTP request (with parameter/query) to this endpoint to your system. then your system parse those parameters, configure them accordingly (i.e. website monitoring --drive--> discord paging).
|
||||
|
||||
but most of the time this kind of process is expected full automatic. so is there any documentation to tell user/customer how to do that ?
|