I've a really nice little reply to this node but, unfortunately, every time I hit preview the server just hangs. Same happens when I try and submit it to my scratchpad.

Other text seems to preview just fine.

You can find the text I'm trying to submit at on my website. Any suggestions as to what's going on are more than welcome :-)

Replies are listed 'Best First'.
Re: Previewing message hangs (not my text)
by tye (Sage) on Jan 13, 2003 at 00:48 UTC

    Works for me. I originally previewed and posted the below (cut'n'pasted from your link) without this prelude. I had no problems. After my node appeared with no problems I edited it to add this prelude.

                    - tye

    If you're enforcing the object type you have to draft in Test::MockObject, which is great, but is also substantially more complex.

    You can still use the self-shunt unit testing pattern with enforced object types and Test::Class if you take advantage of perl's run-time method dispatch.

    For example, consider a class that takes an optional logging object to allow custom logging on an object by object basis.

      Freaky. It's still happening to me. I just tried it on a Mac OS X box with Chimera, also with Safari & Mac MSIE on the same box. Browser just sits there and spins.


      Update: Just tried it using a different ISP and it worked. I presume a proxy must have got itself in a twist. My apologies for the duff bug report.

Re: Previewing message hangs
by PodMaster (Abbot) on Jan 13, 2003 at 02:46 UTC
    I experience this from time to time, and it isn't really a perlmonks issue (most of the time ;D). For me, it's a Browser/DNS issue. I have to frequently flush my ip cache (ipconfig /flush), but then I am on windows using a crappy ISP. Your issue may be a different one, but does this happen with other websites? I happens to me all the time with rt.cpan.org.


    MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
    ** The Third rule of perl club is a statement of fact: pod is sexy.

      No, no problems with other W3 sites. Switching ISPs seems to have fixed the problem so I'm guessing some sort of proxy issue.