Recherche avancée

Médias (0)

Mot : - Tags -/objet éditorial

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (33)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

  • Selection of projects using MediaSPIP

    2 mai 2011, par

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

Sur d’autres sites (4741)

  • http: Stop reading after receiving the whole file for non-chunked transfers

    11 août 2014, par Martin Storsjö
    http: Stop reading after receiving the whole file for non-chunked transfers

    Previously this logic was only used if the server didn’t
    
respond with Connection : close, but use it even for that case,
    
if the server response is non-chunked.
    

    Originally the http code has relied on Connection : close to close
    
the socket when the file/stream is received - the http protocol
    
code just kept reading from the socket until the socket was closed.
    
In f240ed18 we added a check for the file size, because some
    
http servers didn’t respond with Connection : close (and wouldn’t
    
close the socket) even though we requested it, which meant that the
    
http protocol blocked for a long time at the end of files, waiting
    
for a socket level timeout.
    

    When reading over tls, trying to read at the end of the connection,
    
when the peer has closed the connection, can produce spurious (but
    
harmless) warnings. Therefore always voluntarily stop reading when
    
the specified file size has been received, if not using a chunked
    
transfer encoding. (For chunked transfers, we already return 0
    
as soon as we get the chunk header indicating end of stream.)
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DBH] libavformat/http.c

  • Replace ffurl_register_protocol()

    2 octobre 2017, par mahboudz

    I have old code that calls ffurl_register_protocol(), and linked with FFMPEG 3.0.2.

    I’m upgrading to FFMPEG 3.3. It looks like ffurl_register_protocol()n has been deprecated, although there is not a whole lot of mention of the change. Google finds only few mentions, such as this one, where someone is trying to export ffurl_register_protocol() to continue using it.

    Any advice how I should proceed ? How can I replace ffurl_register_protocol() ? Or do I look to export it in the latest FFMPEG ?

  • RTMP Authentication for Wowza

    6 février 2017, par James Oanta

    I have a java encoder that currently does not support RTMP authentication.

    I’ve done some research on how to implement that part this days but the RTMP protocol lacks of documentation regarding this and I couldn’t find anything (very helpful) related to this.

    Basically I have the following url schema : rtmp ://user:pass@wowza_adress:1935/application

    In the official documentation (V1.0) released by adobe there is no specification of any authentication command nor any RTMP authentication reference.

    Could someone give me an hint/example on how this should be done ?

Navigation