binary_to_term atom table overflow threat

[Shawn Pearce]

So what is the best way to deal with the binary_to_term/1
atom table overflow problem (you know, 1 million atom
limit, binary_to_term/1 can make any atoms it pleases)?

Any chance we might see a binary_to_term/2 where if the
second argument is false term's which are atoms in the
input binary and are not already in the atom table are
returned as strings (lists)?  Might not make sense to
do though, given that UBF exists...

-- 
Shawn.

  Your lucky number has been disconnected.