Download turbovnc

Author: s | 2025-04-24

Download do TurboVNC [PT] T l charger TurboVNC [FR] ダウンロードTurboVNC [JA] Tải xuống TurboVNC [VI] TurboVNC herunterladen [DE] 下载TurboVNC [ZH] Download TurboVNC [NL] Ladda ner TurboVNC [SV]

TurboVNC/turbovnc: Main TurboVNC repository - GitHub

Thanks for downloading TurboVNC 3.0.3 Download of TurboVNC 3.0.3 will start in 5 seconds... Problems with the download? Please restart the download. TurboVNC 3.0.3 File Name: turbovnc-3.0.3.x86_64.rpm File Size: 39.47 MB Date Added: August 18, 2023 PriceFree Version3.0.3 Release DateFebruary 27, 2023 PublisherTurboVNC - Publisher's DescriptionTurboVNC is a high-performance, enterprise-quality version of VNC based on TightVNC, TigerVNC, and X.org. It contains a variant of Tight encoding that is tuned for maximum performance and compression with 3D applications (VirtualGL), video, and other image-intensive workloads. TurboVNC, in combination with VirtualGL, provides a complete solution for remotely displaying 3D applications with interactive performance. TurboVNC's high-speed encoding methods have been adopted by TigerVNC and libvncserver, and TurboVNC is also compatible with any other TightVNC derivative.TurboVNC forked from TightVNC in 2004 and still covers all of the TightVNC 1.3.x features, but TurboVNC contains numerous feature enhancements and bug fixes relative to TightVNC, and it compresses 3D and video workloads much better than TightVNC while using generally only 5-20% of the CPU time of the latter. Using non-default settings, TurboVNC can also be made to compress 2D workloads as "tightly" as TightVNC.Features Fine-grained control over the JPEG image quality and level of chrominance subsampling Double buffering on the client side to reduce tearing artifacts in 3D and video applications Flexible and configurable full-screen/multi-screen support Full support for IPv6 Advanced flow control and continuous updates (greatly improves performance on high-latency connections) Authentication with one-time passwords or Unix login credentials (in addition to standard VNC passwords) Access control lists (for sharing VNC sessions with only certain users) Allows security/authentication policies to be set globally for a particular server machine Multithreaded encoding “Lossless refresh” allows a viewer to request a lossless copy of the current screen image, either manually or automatically (after a specified number of seconds of inactivity) High-performance zero-install Java viewer, deployable using Java Web Start, that calls libjpeg-turbo through JNI to achieve native levels of performance Fastest VNC viewer available (that we know of) on OS X and Windows

turbovnc/BUILDING.md at main TurboVNC/turbovnc - GitHub

VirtualGL will only have a limited pool of PBOs (no more than 3) to work with. This is awkward at best, since the TurboVNC Server doesn't necessarily generate a framebuffer update immediately when VirtualGL draws a frame. The VNC server basically acts as another layer of frame spoiling, since it can coalesce multiple frames from VirtualGL into one framebuffer update as a result of the deferred update timer or as a result of the RFB flow control extensions (which prevent updates from being sent faster than the network or viewer can handle them.) At first glance, it might seem possible to make the proposed PBO PutImage extension asynchronous and thereby essentially treat the TurboVNC Server as VirtualGL's image transport thread. In other words, VirtualGL would, within the application rendering thread, use the PBO PutImage extension to request a free PBO from the pool, and TurboVNC would block on that request until a PBO is free, then VirtualGL would fill the PBO with pixels and send back another request notifying TurboVNC that the PBO is ready to transmit. However, that scheme is likely not possible due to the fact that the TurboVNC Server is single-threaded (as are all X servers.) It will probably be necessary for the TurboVNC Server to pre-compress the H.264 pixels within the body of the PBO PutImage function and then to just store those pixels in a holding buffer until the next RFB framebuffer update.Approach #3 seems to be the most promising, but I suspect it would take hundreds of hours of labor to make it happen, and in the grand scheme of things, it may make more sense to wait for Wayland, since Wayland's architecture is much more conducive to the use of frame-based codecs such as H.264 (refer to #18) and probably GPU-based encoding as well. Furthermore, referring to the article on TurboVNC.org, H.264 doesn't necessarily benefit all types of applications. It is clear that it can benefit applications like video players, Google Earth, games, etc., but for ordinary CAD applications, the jury is still out.There are additional challenges inherent with decoding the H.264 stream with reasonable performance. As with JPEG, it would likely be necessary to use some sort of H.264 decoder accessed through JNI in the Java viewers, or perhaps to leverage the built-in decoders on some GPUs (if available.)

Download TurboVNC-2.0.exe (TurboVNC) - SourceForge

Under RHEL and Fedora, /etc/X11/xinit/xinitrc-common includes the following code:RHEL 4-7:# Prefix launch of session with ssh-agent if available and not already running.SSH_AGENT=if [ -z "$SSH_AGENT_PID" ] && [ -x /usr/bin/ssh-agent ]; then if [ "x$TMPDIR" != "x" ]; then SSH_AGENT="/usr/bin/ssh-agent /bin/env TMPDIR=$TMPDIR" else SSH_AGENT="/usr/bin/ssh-agent" fifiFedora 22, 24 (possibly earlier releases as well):# Prefix launch of session with ssh-agent if available and not already running.if [ -z "$SSH_AGENT" ] && [ -z "$SSH_AGENT_PID" ] && [ -x /usr/bin/ssh-agent ]; then if [ "x$TMPDIR" != "x" ]; then SSH_AGENT="/usr/bin/ssh-agent /bin/env TMPDIR=$TMPDIR" else SSH_AGENT="/usr/bin/ssh-agent" fifiIf the SSH_AGENT_PID environment variable is blank, then effectively this code causes the window manager to be launched with ssh-agent, and ssh-agent clobbers the LD_PRELOAD environment variable set by VirtualGL. This was only recently discovered, because I run keychain on all of my development and testing machines, and keychain sets SSH_AGENT_PID, thus working around this issue.The issue can be reproduced in isolation thusly:Configure the machine to run full-blown GNOME 3. On RHEL 7, for instance, this involves setting DESKTOP="GNOME" in /etc/sysconfig/desktop (otherwise it will run GNOME 3 Classic.)/opt/TurboVNC/bin/vncserver -3dwmDISPLAY=:1 vglrun /usr/bin/ssh-agent /opt/VirtualGL/bin/glxspheres64This produces a very similar failure to the one that is produced by attempting to run GNOME 3 in VirtualGL without the SSH_AGENT_PID environment variable set:ERROR: ld.so: object 'libdlfaker.so' from LD_PRELOAD cannot be preloaded: ignored.ERROR: ld.so: object 'libvglfaker.so' from LD_PRELOAD cannot be preloaded: ignored.Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)Xlib: extension "GLX" missing on display ":1".ERROR in line 619:Could not obtain RGB visual with requested propertiesXlib: extension "GLX" missing on display ":1".However, if you swap "vglrun" and "/usr/bin/ssh-agent", it works. Setting SSH_AGENT_PID to some fake value is probably not a good idea, since other applications may try to actually use that value. It makes more sense for xstartup.turbovnc to handle this somehow. I'm looking into that.Known workarounds:Use MATERun keychainModify xstartup.turbovnc so that it executes the WM using VirtualGL and ssh-agent in the right order:if [ -x /etc/X11/xinit/xinitrc ]; then /usr/bin/ssh-agent vglrun /etc/X11/xinit/xinitrcfiNOTE: do not pass -3dwm to vncserver if you do this.. Download do TurboVNC [PT] T l charger TurboVNC [FR] ダウンロードTurboVNC [JA] Tải xuống TurboVNC [VI] TurboVNC herunterladen [DE] 下载TurboVNC [ZH] Download TurboVNC [NL] Ladda ner TurboVNC [SV] Download the TurboVNC Windows installer package (TurboVNC-{version}.exe) from the Download area of the VirtualGL SourceForge web-site. Run the TurboVNC installer. The installation of TurboVNC should be self-explanatory.

Download turbovnc-3.1.tar.gz (TurboVNC) - SourceForge

Efficiency and the need to encode at a fixed frame rate, because it is assumed that-- at least with double-buffered OpenGL applications-- each frame sent through VirtualGL will share few pixels with the previous frame (but, in some cases, the differences will be within the scope of H.264's predictive abilities.)Encoding the video stream is easy, because the pixels are already on the GPU. VirtualGL would simply encode them using NvENC or similar and transmit the H.264 stream directly from GPU memory. But that's where things get dicey. How would we transmit the stream through the TurboVNC Server and to the client? We could implement some sort of "compressed PutImage extension", whereby the compressed stream could be passed through unmodified by the TurboVNC Server and decompressed by the viewer, but this introduces all-new problems:How would we handle window overlapping? The hypothetical compressed PutImage extension would have to communicate the structure of an overlapped window image back to VirtualGL so that it could break the image down into component rectangles and send each separately, or perhaps we could just make the simplifying assumption that, if the window is overlapped or obscured, H.264 will be temporarily disabled for that window.How would we handle combined OpenGL and X operations? An OpenGL/X11 application is well within its rights to request a copy of the OpenGL-rendered pixels using X11 functions (XGetImage(), for instance), assuming that it has called glXWaitGL() to ensure that the pixels have been delivered to the X server. So how would the TurboVNC Server accommodate that request if the OpenGL-rendered pixels are being passed through as an encoded H.264 stream. It would have to keep a copy of the video stream all the way back to the last I-frame, or it would have to somehow notify VirtualGL that it needs an uncompressed copy of the current frame (problematic, since VirtualGL may not have it anymore), or VirtualGL would have to deliver two copies of the frame to the X server-- one compressed and one uncompressed. Delivering two copies isn't a huge deal, since the current VirtualGL/TurboVNC solution already delivers an uncompressed version of the frame. The increase in bus usage would be only incremental, due to the addition of delivering the compressed H.264 version of the frame.How would we ensure that the viewer can handle H.264? This is normally negotiated by the VNC server, and since it has access to all of the

Download turbovnc-.x86_64.rpm (TurboVNC) - SourceForge

Framebuffer pixels, it can (and does) encode those pixels differently for each viewer. Pre-encoding in VirtualGL would require passing some information about the connected viewers back to VirtualGL, so it could determine whether it is OK to use H.264. Also, since the viewer can request a new copy of any region of the remote desktop at any time (and does, via the Lossless Refresh and Refresh features), the server would have to always maintain a copy of the H.264 pixels in uncompressed form, per above. Maintaining a copy of the H.264 pixels in uncompressed form would also be necessary in order to support Automatic Lossless Refresh.Deferred readback and encoding (PBO PutImage extension)"Deferred readback" mode VirtualGL/virtualgl#9 proposes a mechanism for deferring the readback of OpenGL pixels so that readback doesn't occur in the rendering thread but instead occurs in the image transport-- basically the pixels would be copied into a PBO instead of read back, and the image transport would access the PBO and compress the pixels directly from GPU memory (or perhaps even compress the pixels with the GPU.)This could be taken one step further, and instead of the image transport compressing/transmitting the pixels, it could conceivably pass a PBO handle to TurboVNC using some as-yet-to-be-defined custom X extension. This extension could work similarly to MIT-SHM, except that it would allow a PBO handle to be passed in rather than a shared memory segment ID. The TurboVNC Server would then take that handle and copy the pixels into its own framebuffer as well as generate an H.264 frame from them. This would require only an incremental amount of additional bus traffic (the copying of uncompressed pixels from graphics memory into main memory is already occurring now. The only addition here would be copying the compressed H.264 frame from graphics memory into main memory.)The main advantage this has over Approach 2 is that it allows the TurboVNC Server to handle the pixels as it sees fit, rather than enforcing a particular encoding scheme upon it. This greatly simplifies the implementation, since the server can decide whether it wants to use H.264 based on whether a particular viewer supports it, and it can decide to temporarily turn off H.264 and transfer only the unobscured rectangles from an obscured window, etc.One concern here, however, is synchronization. VirtualGL cannot grant the TurboVNC Server access to the PBO for an unlimited period of time, since

Download TurboVNC--x64.exe (TurboVNC) - SourceForge

Update 1.2.1.3 ( only exe all a single zip)-multimon patch-zlib and jpeg libs to latest version-Latest Visual Studio 2017 compilerUltraVNC1.2.1.3.zip Translated winvnc.exe and or vncviewer.exeGermanFrenchSpanishRussianCatalanPortuguezeJapanRemark bins: Never extract the exe direct (via iexplorer) from the zip. If you extract them direct, uac mark the files as unsecure... and winvnc server doesn't work proper. First save as zip then open via explorer...DOCSWord doc is also available, feel free to correct or add things. UVNCLaunch manual options Repeater (exe)UvncLaunchWARNING: In MODE I the repeater works like a proxy. You need to restrict the ip addreses and ports to prevent unwanted access. (repeater settings)RepeaterMirror DriverSourceCode uvnc 1212Changes*********************************************** Ultr@VNC - Latest modifications - History** V1.2.1.1 April 2016Vnchooks: make sure the correct versions are attached, some older crashedServer:-black screen on connection/ grey screen on connection and deadlock-on disconnect server icon stayed yellow, blocking new connections-black viewer with icons without file transfer.-fixed mem leaks/resource leakViewer:-Fix overrun crash-Timeout reconnect fix-Closing no reconnect fix-Auto refresh after idleUpdate jpeg lib** V1.2.1.0 January 2016Server: added rdp session selectServer: added alternate shell when you use another shell the explorer.exe it doesn’t work correct[admin] alternate_shell=myshell.exe rdpmode=1Viewer: added remember last location ( host based)UVNC_LAUNCH: addedFixesArtifacts on win8>Faster reconnect on session switchRepeater:reconnect, some port scanners could kick connections, stability** V1.2.0.9 November 2015*added XZ encoder (small bandwidth)*crash fix*auto mode: better initial settings to avoid coder switch on start*fix 10 second delay win8 with keyboardhelper*w8hook embedded*option Gii encoder adde*memory leaks*added tight encoder patch from Turbovnc project*reconnect timeout in invers mode was increasing on each try, max

Download turbovnc-3.0.tar.gz (TurboVNC) - SourceForge

Skip to content Navigation Menu GitHub Copilot Write better code with AI Security Find and fix vulnerabilities Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes Discussions Collaborate outside of code Code Search Find more, search less Explore Learning Pathways Events & Webinars Ebooks & Whitepapers Customer Stories Partners Executive Insights GitHub Sponsors Fund open source developers The ReadME Project GitHub community articles Enterprise platform AI-powered developer platform Pricing Provide feedback Saved searches Use saved searches to filter your results more quickly //voltron/issues_fragments/issue_layout;ref_cta:Sign up;ref_loc:header logged out"}"> Sign up Notifications You must be signed in to change notification settings Fork 146 Star 866 DescriptionTrying to connect to a server that supports Intel KVM AMT I noticed that Turbo VNC does not work, it authenticates and then the connection is closed with a read error. The RealVNC client works. Apparently it has to do with RFB protocol version 4.0 which is not documented anywhere.More from here: seems to be a known issue to the KVM's use of RFB 4.0, which seems to be a proprietary extension to the RFB protocol. If someone can find an actual specification for this extension, then it's probably something that would be easy to support, but even RealVNC's own specification ( only seems to address versions 3.8, and the community specification that TurboVNC and TigerVNC maintain ( also only goes to 3.8. The thread on Intel's web site above seems to indicate that dropping down to 8-bit might allow it to work with an RFB 3.8 viewer. You can try that by passing "-colors 256" to the TurboVNC Java Viewer.. Download do TurboVNC [PT] T l charger TurboVNC [FR] ダウンロードTurboVNC [JA] Tải xuống TurboVNC [VI] TurboVNC herunterladen [DE] 下载TurboVNC [ZH] Download TurboVNC [NL] Ladda ner TurboVNC [SV]

Download TurboVNC-2.2.exe (TurboVNC) - SourceForge

IRapp was my favorite fast screen sharing server for OS X, but they went bankrupt around June 2016 and their license server was taken down at some point. As of around Oct 2, 2016 my license for iRapp server said it was blocked because it couldn't contact the license server and I could find no way to get it working again. Even a trial license I had a copy of wouldn't install without their license server being up.After some research, I found that Aqua Connect is the only iRapp competitor around that offers an OS X RDP server. In fact, Aqua was first with RDP and they sued iRapp for reverse engineering their product, but lost the case. Aqua is supposedly faster (they've improved on the RDP protocol and call it AAP) but unfortunately they are slow in development. iRapp had OS X El Capitan support a few months after it was released, but when I asked for a trial license from Aqua they said Aqua is still a week or more out from having a beta with support for El Capitan (and this was over a year after EC was released!).So far, I have resisted paying Aqua $249 knowing that their software may become useless with a future macOS update and they might not fix it for 1+ years again.I've tried all the free VNC clients: RealVNC, TightVNC, TigerVNC, UltraVNC, and TurboVNC and they are all laggy in various places, even on a LAN, and each has various problems

Download TurboVNC-3.0.dmg (TurboVNC) - SourceForge

Referring to H.264 isn't necessarily a good fit for VNC, because H.264 is designed for encoding video content with a fixed frame size, and VNC doesn't really have a concept of frames per se. When using frame-based applications (such as video players and 3D applications, i.e. VirtualGL) within VNC, the frames generated by those applications are usually translated into individual RFB framebuffer updates, but with other applications, that is usually not the case. When typing into a terminal window, for instance, only a few pixels may change as you are typing, but H.264 would require that minimally the entire window (if not the whole desktop) be re-encoded every time even the smallest change occurs. This is necessary because H.264 does its own interframe comparison, and thus each encode operation needs access to the entire frame so that it can determine which pixels have changed and generate the interframe-compressed video stream accordingly. For all intents and purposes, H.264 has a constant compression overhead. Every time you compress a frame, it takes about the same amount of CPU time, regardless of how many pixels have changed.Furthermore, the x264 open source H.264 encoder is too slow to be viable for remote 3D in most cases. It would be necessary to use NvENC or another GPU-based encoding mechanism (AMD now has VCE, which is similar in concept) to achieve decent performance with H.264, but this creates other challenges. There are generally three approaches that might work for adding H.264 encoding functionality to TurboVNC with decent performance.Treat the entire VNC desktop as a single H.264 streamAs described above, the main issue inherent in this approach is that it is very inefficient for applications that only update small portions of the screen at a time. Even if only a few pixels have changed, the entire framebuffer has to be re-encoded so that the H.264 codec can detect those changes. Thus, it is likely that this approach would only really make sense if the frame rate was somehow limited. That is, one would want to specify that no more than, say, 30 frames/second would be encoded, so that a lot of small updates could be coalesced into larger updates. The existing deferred update timer mechanism in VNC might provide a means of accomplishing this, although past experience has proven that mechanism to be problematic in terms of performance (due to the fact that the server is single-threaded. Download do TurboVNC [PT] T l charger TurboVNC [FR] ダウンロードTurboVNC [JA] Tải xuống TurboVNC [VI] TurboVNC herunterladen [DE] 下载TurboVNC [ZH] Download TurboVNC [NL] Ladda ner TurboVNC [SV]

Download turbovnc-3.0.3.tar.gz (TurboVNC) - SourceForge

The download jar file contains the following class files or Java source files.1.Download jodd-petite-3.4.5.jar2.Download jodd-proxetta-3.4.4-sources.jar3.Download jodd-proxetta-3.4.4.jar4.Download jodd-proxetta-3.4.5-sources.jar5.Download jodd-proxetta-3.4.5.jar6.Download jodd-lagarto-3.4.3-sources.jar7.Download jodd-lagarto-3.4.3.jar8.Download jodd-lagarto-3.4.4-sources.jar9.Download jodd-lagarto-3.4.4.jar10.Download jodd-lagarto-3.4.5-sources.jar11.Download jodd-lagarto-3.4.5.jar12.Download jodd-lagarto-web-3.4.3-sources.jar13.Download jodd-lagarto-web-3.4.3.jar14.Download jodd-lagarto-web-3.4.4-sources.jar15.Download jodd-lagarto-web-3.4.4.jar16.Download jodd-lagarto-web-3.4.5-sources.jar17.Download jodd-lagarto-web-3.4.5.jar18.Download jodd-petite-3.4.3-sources.jar19.Download jodd-petite-3.4.3.jar20.Download jodd-petite-3.4.4-sources.jar21.Download jodd-petite-3.4.4.jar22.Download jodd-proxetta-3.4.3-sources.jar23.Download jodd-proxetta-3.4.3.jar24.Download jodd-joy-3.4.3-sources.jar25.Download jodd-joy-3.4.3.jar26.Download jodd-vtor-3.4.3-sources.jar27.Download jodd-vtor-3.4.3.jar28.Download jodd-vtor-3.4.4-sources.jar29.Download jodd-vtor-3.4.4.jar30.Download jodd-vtor-3.4.5-sources.jar31.Download jodd-vtor-3.4.5.jar32.Download jodd-bean-3.4.4-sources.jar33.Download jodd-bean-3.4.4.jar34.Download jodd-bean-3.4.5-sources.jar35.Download jodd-bean-3.4.5.jar36.Download jodd-wot-3.2.5-sources.jar37.Download jodd-wot-3.2.5.jar38.Download jodd-mail-3.4.0-sources.jar39.Download jodd-mail-3.4.0.jar40.Download jodd-mail-3.4.1-sources.jar41.Download jodd-mail-3.4.1.jar42.Download jodd-mail-3.4.2-sources.jar43.Download jodd-mail-3.4.2.jar44.Download jodd-mail-3.4.3-sources.jar45.Download jodd-mail-3.4.3.jar46.Download jodd-mail-3.4.4-sources.jar47.Download jodd-mail-3.4.4.jar48.Download jodd-mail-3.4.5-sources.jar49.Download jodd-mail-3.4.5.jar50.Download jodd-servlet-3.4.3-sources.jar51.Download jodd-servlet-3.4.3.jar52.Download jodd-servlet-3.4.4-sources.jar53.Download jodd-servlet-3.4.4.jar54.Download jodd-servlet-3.4.5-sources.jar55.Download jodd-servlet-3.4.5.jar56.Download jodd-core-3.4.2-sources.jar57.Download jodd-core-3.4.2.jar58.Download jodd-core-3.4.3-sources.jar59.Download jodd-core-3.4.3.jar60.Download jodd-core-3.4.4-sources.jar61.Download jodd-core-3.4.4.jar62.Download jodd-core-3.4.5-sources.jar63.Download jodd-core-3.4.5.jar64.Download jodd-swingspy-3.4.3-sources.jar65.Download jodd-swingspy-3.4.3.jar66.Download jodd-swingspy-3.4.4-sources.jar67.Download jodd-swingspy-3.4.4.jar68.Download jodd-swingspy-3.4.5-sources.jar69.Download jodd-swingspy-3.4.5.jar70.Download jodd-upload-3.4.3-sources.jar71.Download jodd-upload-3.4.3.jar72.Download jodd-upload-3.4.4-sources.jar73.Download jodd-upload-3.4.4.jar74.Download jodd-upload-3.4.5-sources.jar75.Download jodd-upload-3.4.5.jar76.Download jodd-props-3.4.3-sources.jar77.Download jodd-props-3.4.3.jar78.Download jodd-props-3.4.4-sources.jar79.Download jodd-props-3.4.4.jar80.Download jodd-props-3.4.5-sources.jar81.Download jodd-props-3.4.5.jar82.Download jodd-3.2-sources.jar83.Download jodd-3.2.6.jar84.Download jodd-3.2.7.jar85.Download jodd-3.2.jar86.Download jodd-3.3-sources.jar87.Download jodd-3.3.1-sources.jar88.Download jodd-3.3.1.jar89.Download jodd-3.3.2-sources.jar90.Download jodd-3.3.2.jar91.Download jodd-3.3.3-sources.jar92.Download jodd-3.3.3.jar93.Download jodd-3.3.4-sources.jar94.Download jodd-3.3.4.jar95.Download jodd-3.3.7-sources.jar96.Download jodd-3.3.7.jar97.Download jodd-3.3.8-sources.jar98.Download jodd-3.3.8.jar99.Download jodd-3.3.jar100.Download jodd-core-3.4.0-sources.jar101.Download jodd-core-3.4.0.jar102.Download jodd-core-3.4.1-sources.jar103.Download jodd-core-3.4.1.jar104.Download jodd-db-3.4.0-sources.jar105.Download jodd-db-3.4.0.jar106.Download jodd-db-3.4.1-sources.jar107.Download jodd-db-3.4.1.jar108.Download jodd-db-3.4.2-sources.jar109.Download jodd-db-3.4.2.jar110.Download jodd-joy-3.4.0-sources.jar111.Download jodd-joy-3.4.0.jar112.Download jodd-joy-3.4.1-sources.jar113.Download jodd-joy-3.4.1.jar114.Download jodd-joy-3.4.2-sources.jar115.Download jodd-joy-3.4.2.jar116.Download jodd-jtx-3.4.0-sources.jar117.Download jodd-jtx-3.4.0.jar118.Download jodd-jtx-3.4.1-sources.jar119.Download jodd-jtx-3.4.1.jar120.Download jodd-jtx-3.4.2-sources.jar121.Download jodd-jtx-3.4.2.jar122.Download jodd-lagarto-3.4.0-sources.jar123.Download jodd-lagarto-3.4.0.jar124.Download jodd-lagarto-3.4.1-sources.jar125.Download jodd-lagarto-3.4.1.jar126.Download jodd-lagarto-3.4.2-sources.jar127.Download jodd-lagarto-3.4.2.jar128.Download jodd-lagarto-web-3.4.0-sources.jar129.Download jodd-lagarto-web-3.4.0.jar130.Download jodd-lagarto-web-3.4.1-sources.jar131.Download jodd-lagarto-web-3.4.1.jar132.Download jodd-lagarto-web-3.4.2-sources.jar133.Download jodd-lagarto-web-3.4.2.jar134.Download jodd-madvoc-3.4.0-sources.jar135.Download jodd-madvoc-3.4.0.jar136.Download jodd-madvoc-3.4.1-sources.jar137.Download jodd-madvoc-3.4.1.jar138.Download jodd-madvoc-3.4.2-sources.jar139.Download jodd-madvoc-3.4.2.jar140.Download jodd-petite-3.4.0-sources.jar141.Download jodd-petite-3.4.0.jar142.Download jodd-petite-3.4.1-sources.jar143.Download jodd-petite-3.4.1.jar144.Download jodd-petite-3.4.2-sources.jar145.Download jodd-petite-3.4.2.jar146.Download jodd-proxetta-3.4.0-sources.jar147.Download jodd-proxetta-3.4.0.jar148.Download jodd-proxetta-3.4.1-sources.jar149.Download jodd-proxetta-3.4.1.jar150.Download jodd-proxetta-3.4.2-sources.jar151.Download jodd-proxetta-3.4.2.jar152.Download jodd-servlet-3.4.0-sources.jar153.Download jodd-servlet-3.4.0.jar154.Download jodd-servlet-3.4.1-sources.jar155.Download jodd-servlet-3.4.1.jar156.Download jodd-servlet-3.4.2-sources.jar157.Download jodd-servlet-3.4.2.jar158.Download jodd-swingspy-3.4.0-sources.jar159.Download jodd-swingspy-3.4.0.jar160.Download jodd-swingspy-3.4.1-sources.jar161.Download jodd-swingspy-3.4.1.jar162.Download jodd-swingspy-3.4.2-sources.jar163.Download jodd-swingspy-3.4.2.jar164.Download jodd-upload-3.4.0-sources.jar165.Download jodd-upload-3.4.0.jar166.Download jodd-upload-3.4.1-sources.jar167.Download jodd-upload-3.4.1.jar168.Download jodd-upload-3.4.2-sources.jar169.Download jodd-upload-3.4.2.jar170.Download jodd-vtor-3.4.0-sources.jar171.Download jodd-vtor-3.4.0.jar172.Download jodd-vtor-3.4.1-sources.jar173.Download jodd-vtor-3.4.1.jar174.Download jodd-vtor-3.4.2-sources.jar175.Download jodd-vtor-3.4.2.jar176.Download jodd-wot-3.2-sources.jar177.Download jodd-wot-3.2.6-sources.jar178.Download jodd-wot-3.2.6.jar179.Download jodd-wot-3.2.7-sources.jar180.Download jodd-wot-3.2.7.jar181.Download jodd-wot-3.2.jar182.Download jodd-wot-3.3-sources.jar183.Download jodd-wot-3.3.1-sources.jar184.Download jodd-wot-3.3.1.jar185.Download jodd-wot-3.3.2-sources.jar186.Download jodd-wot-3.3.2.jar187.Download jodd-wot-3.3.3-sources.jar188.Download jodd-wot-3.3.3.jar189.Download jodd-wot-3.3.4-sources.jar190.Download jodd-wot-3.3.4.jar191.Download jodd-wot-3.3.7-sources.jar192.Download jodd-wot-3.3.7.jar193.Download jodd-wot-3.3.8-sources.jar194.Download jodd-wot-3.3.8.jar195.Download jodd-wot-3.3.jar196.Download jodd-madvoc-3.4.3-sources.jar197.Download jodd-madvoc-3.4.3.jar198.Download jodd-madvoc-3.4.4-sources.jar199.Download jodd-madvoc-3.4.4.jar200.Download jodd-madvoc-3.4.5-sources.jar201.Download jodd-madvoc-3.4.5.jar202.Download jodd-wot-3.1.0-sources.jar203.Download jodd-wot-3.1.0.jar204.Download jodd-wot-3.1.1-sources.jar205.Download jodd-wot-3.1.1.jar206.Download jodd-props-3.4.0-sources.jar207.Download jodd-props-3.4.0.jar208.Download jodd-props-3.4.1-sources.jar209.Download jodd-props-3.4.1.jar210.Download jodd-props-3.4.2-sources.jar211.Download jodd-props-3.4.2.jar212.Download jodd-3.1.0-sources.jar213.Download jodd-3.1.0.jar214.Download jodd-3.1.1-sources.jar215.Download jodd-3.1.1.jar216.Download jodd-3.2.5-sources.jar217.Download jodd-3.2.5.jar218.Download jodd-3.2.6-sources.jar219.Download jodd-3.2.7-sources.jar220.Download jodd-joy-3.4.4-sources.jar221.Download jodd-joy-3.4.4.jar222.Download jodd-joy-3.4.5-sources.jar223.Download jodd-joy-3.4.5.jar224.Download jodd-jtx-3.4.3-sources.jar225.Download jodd-jtx-3.4.3.jar226.Download jodd-jtx-3.4.4-sources.jar227.Download jodd-jtx-3.4.4.jar228.Download jodd-jtx-3.4.5-sources.jar229.Download jodd-jtx-3.4.5.jar230.Download jodd-db-3.4.3-sources.jar231.Download jodd-db-3.4.3.jar232.Download jodd-db-3.4.4-sources.jar233.Download jodd-db-3.4.4.jar234.Download jodd-db-3.4.5-sources.jar235.Download jodd-db-3.4.5.jar236.Download jodd-bean-3.4.1-sources.jar237.Download jodd-bean-3.4.1.jar238.Download jodd-bean-3.4.0-sources.jar239.Download jodd-bean-3.4.0.jar240.Download jodd-bean-3.4.2-sources.jar241.Download jodd-bean-3.4.2.jar242.Download jodd-bean-3.4.3-sources.jar243.Download jodd-bean-3.4.3.jar