Saita HTTP proxy na vlcj ta MediaPlayerFactory

vlcj yana ba da damar samun kafofin watsa labarai ga native LibVLC. Mika zaɓin proxy lokacin gina MediaPlayerFactory da ake amfani da shi don ƙirƙirar player:

import uk.co.caprica.vlcj.factory.MediaPlayerFactory;

var factory = new MediaPlayerFactory(
    "--http-proxy", "http://proxy.example.net:8080");
var player = factory.mediaPlayers().newMediaPlayer();

Zaɓin da ƙimarsa suna cikin daban-daban constructor arguments, daidai da tsarin argument na LibVLC. Player ɗin da aka samu yana amfani da native instance configuration na wannan factory. Ƙarshen HTTP daga jerin HTTP proxy zai iya cika argument ɗin proxy don samun damar jama'a da aka yarda.

Canza property ɗin http.proxyHost na Java ba ya maye gurbin wannan native HTTP setting ɗin kai tsaye. Hakazalika, media player da aka ƙirƙira daga wata factory na iya samun wani configuration dabam.

Tabbatar cewa sigar LibVLC da aka loda da module ɗin samun damar HTTP ɗinta suna goyon bayan zaɓin. Mika argument ɗin da ba a goyon baya ta Java ba ya ƙara wannan fasalin ga native library.

Wannan yana saita damar samun kafofin watsa labarai na HTTP. Ba ya mai da kowane media protocol, kamar RTSP ko UDP, zuwa HTTP proxy request. Saki player ɗin sannan factory ɗin da ya mallaka ta hanyar al'adar vlcj lifecycle na application ɗin.