THREDDS License Change

TDS

As we approach the first public beta of version 5.0 of the THREDDS Data Server (TDS), we have decided to revisit our software license. Currently, both NetCDF-Java and the TDS are released under the same license that the netCDF C library uses, which is a license that was "home grown" at UCAR. It's usually called an "MIT-style license," though it is perhaps more similar to the BSD-3 Clause license. Rather than continue to use the "home grown" license, we will be moving to a standard, off-the-shelf BSD-3 license, bringing the TDS and NetCDF-Java packages more in line with standard practice within the Open Source community.

[Read More]

Event Notification for Thredds Servers

Periodically some of the Thredds servers run by Unidata get seriously overloaded. One cause is because external users poll the Thredds server to see what has changed. If the polling rate is too high then the performance of the Thredds server can seriously deteriorate.

I am proposing here to mitigate this problem by allowing Thredds servers to generate events that signal changes that might be of interest to users. Then, instead of polling, these users can watch for specific changes events and use that information to update their local databases (or whatever).

[Read More]

The Death of Server-Side Computing

For a number of years, the Unidata Thredds group has been in the process of "implementing" server-side computation Real-Soon-Now (as the saying goes).

Events have overtaken the previous notion of server-side computing and here we try to codify a replacement that uses a separate server model based on Jupyter (an offshoot of IPython).

From the point of view of Unidata, Jupyter provides a powerful alternative to roll-your-own server-side computing. It supports multiple, "real" programming languages. It is a server itself, so it can be co-located with an existing Thredds server. And, most importantly, it is designed to execute small programs written in any of its supported languages.

We are proposing to implement server-side computing for Thredds by using one or more co-located Jupyter servers. This document elaborates on the capabilities and required support infrastructure to make this proposal operational.

[Read More]

Proposed Thredds Architecture Changes for OSGI/JigSaw

This post provides some preliminary ideas on the consequences of moving TDS to use OSGI or JigSaw.

[Read More]

New TDS Cloud Architectures: Proposal 1

The Thredds Data server (TDS) was designed to operate in a client-server architecture. Recently, Unidata has moved TDS into the cloud using its existing architecture.

There seems to be agreement inside Unidata that we need to begin rethinking that architecture to adapt to the realities of the cloud.

[Read More]
Unidata Developer's Blog
A weblog about software development by Unidata developers*
Unidata Developer's Blog
A weblog about software development by Unidata developers*

Welcome

FAQs

News@Unidata blog

Recent Entries:
Take a poll!

What if we had an ongoing user poll in here?

Browse By Topic
  • feed AWIPS II (13)
Browse by Topic
« April 2018
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
     
       
Today