Sergio,

You might take a look at the talk I gave on Voyage/Tugrik at ESUG(slides[1], video[2]). The project is in a functional, but roughed out stage --- but the main idea behind it is that with GemStone as the db serve, you are dealing with Smalltalk objects on both the client and server ...�� Voyage Server Blocks allow you to write code on the client that is executed against objects on the server ... STON is used for serialization/materialization ... Voyage Server Blocks let you blur the lines as to where do the objects live and where does the code execute ...

Currently Tugrik uses MongoTalk as the model for Voyage-style interactions between client and server, but Voyage Server Blocks (which are not a feature of MongoTalk) may be useful on their own ...

In the talk, I mention that I am looking for partners in pushing Voyage/Tugrik forward, because I think that real users with real problems are needed to drive the project forward --- I am more interested in meeting real developer needs, than building something that makes me happy:)

MongoTalk was originally chosen to make it practical for folks already using Voyage/Mongo to easily kick the tires on Voyage/Tugrik, but I don't think that it is necessary to stay coupled to MongoTalk. Michal Balda is looking at something "simpler than Tugrik+MongoTalk+Voyage" and I wish that I could be in Zurich to see his presentation next week[3]:) as I want to support his efforts ...

Dale

[1] http://www.slideshare.net/esug/tugrik-a-new-persistence-option-for-pharo

[2] https://www.youtube.com/watch?v=YwlUdRaqTwE&feature=youtu.be

[3] http://forum.world.st/ANN-Zurich-Smalltalk-Meetup-Nov-8th-2016-tt4919147.html

Hey, all..

One of the things that I find SUPER necessary when developing an app is to be able to grab data from somewhere else and quickly and easily work on it from my machine.

For instance, when I get a bug report that smells funny, the first thing i sometimes do is run a script that grabs the production data, and populates my local database with that data.

i am fleshing out a project that i would really like to use Teapot (REST) for. i could then write several front ends in whatever framework/language.

I was thinking about using Voyager, but the problem is, the data is VERY relational (see below, if interested).. objects are linked to each other fairly tightly. I don���t know if this would be the way to handle the data, as there would be lots of duplication using mongodb as a datastore.

Of course, my first thought is Gemstones, but I don���t know how to grab the production data and pull it into my local development system.

Does anyone have any thoughts on this?��

For those curious about the data design, i am setting up a REST server for an collaborative internet radio application���

- there would be a global pool of stations (just streaming urls with metadata, really)

- each user can select from or contribute to the global pool

- users can add tags to stations (or search through the global stations based on tags)

- users can attach comments to stations

not complex or intimidating at all, and super easy to model in smalltalk, but not sure about how to store data so that I can quickly grab production data and troubleshoot if if necessary.

Thanks!

----
peace,
sergio
photographer, journalist, visionary

Public Key:��http://bit.ly/29z9fG0
#BitMessage��BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
http://www.Village-Buzz.com
http://www.ThoseOptimizeGuys.com
http://www.coffee-black.com
http://www.painlessfrugality.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101