awakenedviskasha / hyperspace Goto Github PK

Description

A Memoization module is needed in order to reduce the number of request.

Workflow

• [A.I.R.A] Story
• [] Implementation Backlog
• [] Integration

Story

• [F1-S1] When an HyperSpace receive a request, the HyperSpace will check its Memoization Module.
• [F1-S2] IF the Memoization Module has a similar quest saved it will return what was the response of that request if the request was responded a certain amount of time before.
• [F1-S3] IF the Memoization Module does not have the request saved or if the request is too old, the HyperSpace will do the request.
• [F1-S4] If the request is succesful, the Module will save the request and result.

Implementation Backlog

• [F1-S1-I1] .....

• [F1-S1-I2] .....

• [F1-S2-I1] .....

Integration

• Pending since //**
• Reviewed by mr **, the // : accepted/refused (link to post of refusal)
• Planned for the version ..*
• Done in version ..* the //**

Hello fellow Viskashas, I am QuestioningViskasha.

I was using HyperSpace when I realized I was creating ContactCard for my Distributed Objects. Maybe we should make it a basic feature for HyperSpace.

Good luck for the future !

Hello, I'm AV-Issue !

I hope you are doing well in life and all !

I got this error when I tried to retrieve an impostor from an hyperspace. Can you help me ?

TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'Maestro'
    |     property 'myPublisher' -> object with constructor 'Publisher4HyperSpace'
    --- property 'object' closes the circle
    at JSON.stringify (<anonymous>)
    at stringify (D:\dev\cabaretRuns\Run1Prototype\node_modules\express\lib\response.js:1150:12)
    at ServerResponse.json (D:\dev\cabaretRuns\Run1Prototype\node_modules\express\lib\response.js:271:14)
    at ServerResponse.send (D:\dev\cabaretRuns\Run1Prototype\node_modules\express\lib\response.js:162:21)
    at functionSocket (D:\dev\cabaretRuns\Run1Prototype\node_modules\@awakenedviskasha\hyperspace\CommPost\CommPost.js:39:25)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

Thanks for your help !

Hello,

I wish I could publish at "root url", unfortunately, you have to specify an hyperspace name and this name is used for the url pathing of published methods which is not what you always want to happen.

Maybe the publishing pathing should be reworked.

Description

Contact Card contains the needed informations in order to reach a distributed object. It would be very practical if you can just pass the Contact Card to Hyperspace in order to request a distributed object.

Workflow

• [] Story
• [] Implementation Backlog
• [] Integration

Story

To be Done.

Integration

To be Done.