3 ms·

Seems like Trigger's definateyy on a roll lately with all of this integration/ease of development and tutorials. I haven't heard of Trestle Chain before. But

Seems like Trigger's definateyy on a roll lately with all of this integration/ease of development and tutorials. I haven't heard of Trestle Chain before. But I have experienced these problems with slow network on my mobile website. It's a pain, sometimes it takes a second or so to load a simple AJAX + render some HTML. Might dive deeper with Trestle and Trigger . Anyone have any experience with Trestle/the performance?

jamroom 15y ago
I'm the co-founder of Trestle (Brian), and this is something that my partner Sham and I struggled with as well as we both have created apps that relied heavily on a server backend. With the Chain Server you basically bundle your API calls into "chains" that you then send over to the server in 1 shot - it's actually really slick. Of course not all API calls can be bundled this way since they are more of a "one shot" type call, but if you want to store images, audio, user info, objects, etc. and those items have relationships, you can do it all in one round trip. Our clients make it super easy to make a chain and execute it too. We're looking for developer feedback, so please let me know if you have any suggestions or questions - we're all ears. Thanks!
- lsb 15y ago
  The chainable API calls looks pretty convenient for bulk uploads. Is there any way of lifting the 5-second restriction? What sort of limits do you foresee in how many key-value pairs can get stored?
  - jamroom 15y ago
    The 5 second restriction is only on our Custom NodeJS service - that doesn't apply to the Chain Server. For the custom service that can be increased if needed, we just want to try to limit any runaway processes. The DB backend (Object Database) has a limit of ~240 key value pairs (attributes) per item, but with the Chain Server you could effectively "link" multiple objects together to go beyond that if you wanted. Note that all our media services allow you to save arbitrary data with each media item as well, so you can store your meta data with your media item and not have to create a separate entry in the object database to store that. Hope this helps!

jamroom 15y ago

I'm the co-founder of Trestle (Brian), and this is something that my partner Sham and I struggled with as well as we both have created apps that relied heavily on a server backend. With the Chain Server you basically bundle your API calls into "chains" that you then send over to the server in 1 shot - it's actually really slick. Of course not all API calls can be bundled this way since they are more of a "one shot" type call, but if you want to store images, audio, user info, objects, etc. and those items have relationships, you can do it all in one round trip. Our clients make it super easy to make a chain and execute it too. We're looking for developer feedback, so please let me know if you have any suggestions or questions - we're all ears. Thanks!

lsb 15y ago
The chainable API calls looks pretty convenient for bulk uploads. Is there any way of lifting the 5-second restriction? What sort of limits do you foresee in how many key-value pairs can get stored?
- jamroom 15y ago
  The 5 second restriction is only on our Custom NodeJS service - that doesn't apply to the Chain Server. For the custom service that can be increased if needed, we just want to try to limit any runaway processes. The DB backend (Object Database) has a limit of ~240 key value pairs (attributes) per item, but with the Chain Server you could effectively "link" multiple objects together to go beyond that if you wanted. Note that all our media services allow you to save arbitrary data with each media item as well, so you can store your meta data with your media item and not have to create a separate entry in the object database to store that. Hope this helps!