Add a function that returns all of the available QB field types.

she can be a Customer and a Vendor).  Enumerate the enabled mappings
in hook_user:load

Adding some more informative error messages
Setting QBWC to stopOnError, which is what I think we want most of the time

can be accessed from other modules.

heft to this here module, but will be used for field-mapping applications and
validation.

I'm pretty sure these data structures will change, so be careful, and drop me
a line if you're using this so I know you're out there..

Maps a quickbooks value from the qb_data API to a CCK field.  The design goal
is then to have other CCK values map to Quickbooks fields, so you can store
as much or as little Quickbooks data as you'd like to store in your nodes.

When your nodes are updated, the records are flagged for an update into
Quickbooks.  Similarly, when QB data changes, your nodes are updated on the
next QBWC request.

This is an interim commit, and the field  mappings don't actually work yet.
But it's a start and it rocks! Go me!

Added a hook_qbwc_request_alter, which lets your module add values to request
and specify additional callbacks.

This isn't complete, and the data structure will likely change, so don't go
depending on this yet!

This module imports and tracks entity information from Quickbooks.  For example,
it can facilitate the import/export of all customers, all products, etc.

The QB information this module stores for each entity record is limited to
Quickbooks' ListID ( internal identifier ), Name, and Active status.  It also
stores internal records required to update or sync values.

The intended use of this module is to store skeletal values sufficient for
listing records and tracking their updates; and use other modules ( e.g. a CCK
field module, forthcoming) to manage other values and business rules.

It's a work-in-progress, of course.

internally consistent.

- hook_qbwc_response is DEPRECATED.  Instead, your hook_qbwc_request should
  include a 'callback' array, which defines the function(s) you want to call
  with the result data.
- Results are passed to these callbacks as arrays, not as the XML response.
  This is more consistent with how you're passing data to the API.
- In keeping with how sarvab is using the API, you can also pass a 'data' element.  Thus, hook_qbwc_request looks like:
function hook_qbwc_request() {
  return array(array(
    'name' => 'CustomerQueryRq',
    'callback' => array('my_qbwc_response'),
    'data' => array('I LIKE BUNNIES' => TRUE),
  ));
}
And your callback looks like:
function my_qbwc_response($response=array(), $data=array(), $status, $message) {}

apparently I'm in the minority.

  - Move infrequently-used admin form and qwc file callbacks to qbwc.admin.inc.
  - Move the qbwc() callback to its class file.

It was a little silly, because your module has to do a bunch of work to decide
whether or not to return TRUE on this function (which indicates that you want
to make requests)  And then, your module is subsequently called upon to do
a similar amount of work to actually make these requests.

Instead, the presence of requests found in the hook_qbwc_request() invocation
is used to determine whether the session should continue. This probably won't
break anything, but any qbwc_authenticate code is unused and should be removed.

Other changes:

- Added qbwc_set() and qbwc_get() functions, which are wrappers for information
  that is stored in the session.  You should use these to stash your goods
  rather than interacting with $_SESSION directly.

- Added qbwc_request_queue() API function.  It is automatically populated with
  the values from the initial call to hook_request.  You can store subsequent
  requests by calling qbwc_request_queue($request), and it will get called
  on the next passthru.

- Things are most likely re-broken.  You can thank me later for that.

- Quickbooks' Web Connector now connects and authenticates to the server
- Session tables getting created and populated properly.
- Session open, request and close 'works'

Still need:
- Better / proper parsing of request hooks into QBXML.  Without this, it won't
  work at all.  So hang tight!