Open Chriscbr opened 2 years ago
Hi,
This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Keep
Another idea suggested by @eladb is to introduce a Blob
type that represents an arbitrary piece of data:
What about binary data? For example, if you store a PNG in a bucket and want to
bucket.get()
it, it should return something likeBuffer
orBlob
?I would argue that the non-generic bucket APIs should likely use
Blob
instead ofJson
and that there should beJson.fromBlob(b)
Hi,
This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Wing should have a type, or group of types, that are defined as serializable. These types are useful for cloud application development because when a function call receives an argument in Wing, it's possible the function will be executed on another machine in the cloud. In these cases, there needs to be a serialization mechanism for the argument to be passed without data loss.
For example:
Since this class mutates class-external state in its methods (through
PersonRegistry
), it's not possible to send aPerson
class instance between cloud resources without introducing problems. For example, if cloud function A created aPerson
instance and gave it to cloud function B, how would B callingaddNeighbor
update the originalPersonRegistry
in A's runtime - in a way that adheres to ACID (or at least doesn't surprise users)? I think this is currently out of scope for Wing.Open questions: