thoughtbot Build Phase #63

63: For All Intensive Purposes | Build Phase

request cache sync state queueとか

push notification
provisioning profile
entitlement issue

---

get out here
vocal warm up
bank loan
brown cow
skype crashed
get into
thursday
good sandwitch
witchcraft
poached peirs
toungue
slack
dont podcast
three days ago
request cache
reasonable thing
no syncronyzation
ignoring conflict
sky coredata
enterprisy
remote database
assumption
offline
goes
office
no network access
addition
deletion
modification
replay
get access
remote server
replaying
network request
cloud kit
nice way
transparent
tell api client
weird
queue
request
bottom of stuck
simple explanation
new request
bottom of stuck
app terminated
pipeline request
ns operation
havent done api client
light weight
operation
created at timestamp
sets date
queue
creates
cache
wrapper
conform
semantic wrapper
first operation
save the cache
weird
singleton
visualizing
edge cases
huge problems
end up with multiple queue
network access
grab
execute request
execute remaining request
succeeds
proceeds
nil back
just fail
big problem
real quick
implicitly
singleton
object representation
requirement
state
cache is state
trust
one request fails
replayed
reset data
first launch
flash queue
order
sync
cache first launch
havent fully
ipads in sync
pull information
own database
literary
checking
take response
persisting
completion block
doesnt matter
store
request
interspection
dynamically
mess
one hand
definitely simpler
get cache
foundation
replay failed
specific state
core data
flash queue
fifo
big problem
dropbox
very simplified concept
weird
two weeks
spiking
considering
chunk
worries me
tdd
maybe wrong
file access
mocks
test queue
cache
all of cache
part of cache
test cache
request
cache
archiver
wish
disable disk access
dont have access
this is wall
file manager
cutting off
basic method
stub
singleton dictionary
url
filepath
useful
atomic
put that data into dictionary
mock
archiver unarchiver
shut off disk access
general idea
visualizing
realizing
where
background
completion block
hitting disk
background thread
actual kicking off
more work
easy way
keep main thread
network thread
syncronizing
general
ansumple
some point
save you from
watching
swlite
lot of it
webdav
object representation
deal with
different backend
icloud
no support
2.0 not free
in and out
mental model
research
longer project
sync engine
money pais off
switch geer
push notification
everything fine
provisioning profile
app id thing
different entitlement
entitlement issue
app id
remote notification
fetch completion handler