[Glass] Seaside object log

Yanni Chiu via Glass glass at lists.gemtalksystems.com
Tue Jul 5 12:42:40 PDT 2016

Taking inspiration from
http://mutabit.com/offray/blog/es/entry/ds-twitter-mockup, how about using
Fuel serialization/deserialization to a SQL database blob. So the trimmed
object-graph, from which the request/response strings are generated, would
be serialized to a SQL database. For replay, you could deserialize the
blobs from the database. The SQL database would not burden GemStone with
debug log information, and would avoid the mess of log files. It would
introduce another point of failure though - but maybe not, if you consider
that the filesystem can always fill up.

On Tue, Jun 28, 2016 at 7:34 PM, Richard Sargent via Glass <
glass at lists.gemtalksystems.com> wrote:

> A customer is considering moving their application to GemStone-based
> Seaside.
> They have a feature in their application that they would like to preserve,
> at least in spirit. Can anyone advise me on whether it's possible and
> practical, and if so what the approach would entail?
> Because their system is a "REST-like" two-tier application, they can record
> the request and response strings they use to exchange data between the
> client Seaside machine and the GemStone server. The strings are Smalltalk
> expressions, so they can be debugged interactively when there are problems
> or even to recreate specific successful scenarios.
> They have expressed no prior constraints on how it should be done, but they
> want the comparable ability to capture requests and responses, both
> successes and failures, and be able to rerun them and debug them.
> Thanks everyone!
> --
> View this message in context:
> http://forum.world.st/Seaside-object-log-tp4903954.html
> Sent from the GLASS mailing list archive at Nabble.com.
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20160705/9ec1d026/attachment.html>

More information about the Glass mailing list