servers with huge state terms
Thu Dec 14 12:04:41 CET 2000
A very dirty hack would be to convert the tuple to a list before storing it
in your state and back to a tuple before using it!
> -----Original Message-----
> From: Luke Gorrie [mailto:]
> Sent: 14 December 2000 10:45
> Subject: servers with huge state terms
> I have a server process (gen_fsm) whose state is a very large
> term. This is a problem because when I get a crash report it's really
> long and hard to read - I've done things like ask xterm to have a
> thousand-line scrollback as a workaround.
> I'm tempted to move the larger parts of the state into an ets table
> (which would be pretty suitable, but I prefer the tuple) so that the
> server's state is more stringifyable - but does anyone know another
> approach for this sort of thing?
NOTICE AND DISCLAIMER:
This email (including attachments) is confidential. If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents. We cannot accept liability for any breaches of
confidence arising through use of email. Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions. We will not accept responsibility for any commitments
made by our employees outside the scope of our business. We do not warrant
the accuracy or completeness of such information.
More information about the erlang-questions