Ticket #613 (closed issue: fixed)

Opened 13 years ago

Last modified 11 years ago

[DS] Delivery has been stalled

Reported by: selatham Owned by: spascoe
Priority: required Milestone: BETA+Services
Component: ndg2 Version:
Keywords: Delivery Cc: hsnaith

Description

At the last Project Board we prioritised developer's time and decided to 'park' Delivery. It's still particularly required by NOCS whose data is mostly offline. What's the way forward?

Change History

comment:1 Changed 13 years ago by selatham

  • Component changed from T06_Vocabulary to T05_Delivery

comment:2 Changed 13 years ago by spascoe

  • Cc hsnaith added

The utility and feasibility of using pybbftp may depend on NOCS' requirements. For instance:

  • Is delivery imagined as the primary mechanism of getting data to end users?
  • Technical level of end users. pybbftp was proving difficult to make stable as a multi-distribution linux binary (the source is highly dependent on fairly low level system calls).
  • Volume of data needed to be delivered. Is high throughput essential, or do we just need a NDG-security enabled file transfer mechanism?

There are other alternatives that could be investigated: Adding NDG-security handlers to Pro-FTP, using pydap with a NDG-security WSGI middleware layer.

The problem for me is that I am unable to reliably estimate how much effort would be required to make pybbftp work reliably as a end-user application componenent that works on more than one linux distribution.

comment:3 Changed 13 years ago by selatham

Would like not to do but - We (esp Helen) need some method for getting potentially large amounts of data (and off-line).

comment:4 Changed 13 years ago by selatham

Ag's comment:- Why can this not be done by FTP/HTTP. You can shift large amounts of data it just takes a while. I reckon that this is a low priority compared to getting some of the core services in. If you have core services that actually allow a user to select and get the stuff they are a after, then they won't mind waiting a while to get it home.

comment:5 Changed 12 years ago by lawrence

  • Priority changed from critical to required
  • Owner changed from lawrence to spascoe
  • Milestone changed from BETA to BETA+Services

I think the way forward is to use the proposed WPS, which we expect to have a prototype of at the end of June. I'm handing this off to Stephen so he has this use case at the back of his mind.

comment:6 Changed 12 years ago by spascoe

  • Status changed from new to closed
  • Resolution set to fixed

Delivery will be accomplished through either calls to the CSML-API service or a WCS.

comment:7 Changed 11 years ago by lawrence

  • Keywords Delivery added; ProjectBoard removed
  • Component changed from T05_Delivery to ndg2

moved to component ndg2 (obsolete) as part of ndg2 cleanup

Note: See TracTickets for help on using tickets.