I've looked at using MHP on an IPTV network in the past, and there is nothing major that stops JavaTV being used in this role.
The main things that cause potential problems with MHP is the application signalling/loading and SI access: IPTV systems typically use different approaches to this, and so the current MHP APIs aren't very well-suited to many existing IPTV networks. The DVB-IPI specification may change this as it starts to become adopted more widely, but we'll have to wait and see.
JavaTV has avoided these by being fairly platform-neutral and not specifying things like application signallingand how application files are loaded: these need to be specified for an IPTV platform, but that's not really a JavaTV problem. The JavaTV APIs as they stand can probably work OK.
The biggest challenge is really a system integration issue: integrating the JavaTV SI APIs with the head-end systems provided by the middleware manufacturers and integrating things like VOD services, etc.
Steve.
See my reply to Sarah up a few items. Java TV is very much for IPTV!
To connect the dots, there are two specifications to choose from: GEM-IPTV and MHP-IPTV. Both exist in draft form, but GEM-IPTV hasn't quite been published yet. It's part of GEM 1.2, which may be on www.mhp.org before the end of this month.
I'll be giving a presentation on the GEM-IPTV and MHP-IPTV at an ITU-T study group on IIPTV next week.
Cheers,
Bill
JavaTV needs no modifications to work on IPTV.
The problem is that a lot of elements needed to run JavaTV applications are mot defined by thre JavaTV specification, but by specifications that use it. For instance, JavaTV says nothing about how applications are signalled, downloaded to the STB or launched. Specifications like MHP or OCAP which use JavaTV fill in these gaps for DVB and OpenCable networks respectively, but there's nothing like that for IPTV at the moment (although I'd be very interested in seeing what's happening with GEM-IPTV and MHP-IPTV, because it sounds like those fill many of these holes).
Steve.