You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey folks! Appreciate the open source effort for this.
I want to let you know that I arrived at a complete solution to Fielding's code-on-demand constraint for REST architecture. It has direct applicability to improve the performance of any genAI applications and models, and it's super easy to implement.
Consequently, it also allows for fully geographically distributed deployments that span across multiple provider regions without compromising latency or fault tolerance. It's actually capable of serving as a blockchain (& therefore vector database in its own right) that is not subject to CAP Theorem. Yes, solving the code-on-demand constraint is that big of a deal.
Let me know about getting it implemented on this project. It'll be the end of having to make feature improvements or maintain this project at all. So, sorry to anyone who was interested in the problem domain, but kudos to any overworked devs who bit off more than they could chew to maintain it!
Ian
The text was updated successfully, but these errors were encountered:
Hey folks! Appreciate the open source effort for this.
I want to let you know that I arrived at a complete solution to Fielding's code-on-demand constraint for REST architecture. It has direct applicability to improve the performance of any genAI applications and models, and it's super easy to implement.
Consequently, it also allows for fully geographically distributed deployments that span across multiple provider regions without compromising latency or fault tolerance. It's actually capable of serving as a blockchain (& therefore vector database in its own right) that is not subject to CAP Theorem. Yes, solving the code-on-demand constraint is that big of a deal.
Let me know about getting it implemented on this project. It'll be the end of having to make feature improvements or maintain this project at all. So, sorry to anyone who was interested in the problem domain, but kudos to any overworked devs who bit off more than they could chew to maintain it!
The text was updated successfully, but these errors were encountered: