Ticket #381 (closed task: wontfix)

Opened 16 years ago

Last modified 14 years ago

Remove client-side elementtree/lxml requirement

Reported by: desai Owned by: desai
Priority: major Milestone: Bcfg2 1.0.0 Release
Component: bcfg2-client Version:
Keywords: Cc: [email protected]


The use of xml documents as a transport format predates the use of xml-rpc for client/server communication. Now that we are using xml-rpc, we can build a set of functions that use native xml-rpc datatypes. This has two benefits:

  • Remove the overhead of double-encoding all traffic
  • Removing the lxml/elementtree client-side requirement


Change History

comment:1 Changed 16 years ago by desai

  • Milestone changed from Bcfg2 0.9.1 Release to Bcfg2 0.9.2 Release

comment:2 Changed 16 years ago by desai

  • Status changed from new to assigned
  • Milestone changed from Bcfg2 0.9.3 Release to Bcfg2 0.9.4 Release

comment:3 Changed 16 years ago by dclark

comment:4 Changed 15 years ago by desai

  • Milestone changed from Bcfg2 0.9.5 Release to Bcfg2 0.9.6 Release

comment:5 Changed 14 years ago by solj

  • Milestone changed from Bcfg2 0.9.6 Release to Bcfg2 1.0 Release

comment:6 Changed 14 years ago by desai

  • Status changed from assigned to closed
  • Resolution set to wontfix

This isn't going to happen until we *really* rework the client server api. Closing.

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.