When accessing the camera on mydlink, or on a browser using http://x.x.x.x/mjpg.cgi, I would expect the net bit rate to be substantially less than for a sequence of jpg's, since true motion-jpg uses a lossy form of intraframe compression typically yielding a 20:1 data reduction (according to wikipedia). Indeed, I can readily see this reduction in mjpg clips made on my Canon S5is camera.
It's not clear whether that is happening with the d-link DCS-930L camera (640x480, quality "high", java). The mydlink app "Info" on the iPad2 (802.11n; no other apps running; no other streams to computer) shows these data rates (basically static scene, a few leaves moving):
1 fps ~ 605 kbps actual fps ~0.2 drops connection
5 fps ~350-1075 kbps initially went to ~3fps, then dropped to vary 1 to 2 fps
7 fps ~600-1600 kbps initially went to ~3fps, then dropped to vary 1 to 3 fps
15 fps ~68 kbps actual fps ~0.2 drops connection
My DCS-930L is not stable enough to perform these tests! – mydlink drops connection repeatedly, saying "Timed out"

or "check internet settings" ... grrr ... sigh ... product failure ...
I was trying to establish that the DCS-930L, unlike the DCS-932L, MAY be implementing true mjpg ...