Interesting idea. I'm not sure there's any precedent to host a project-specific web service on drupal.org, though it would be pretty cool if we could get authorization for something like that. It would likely be seen as a "big ask," but there's no harm in trying.
Anyhow, we have a good chunk of time to accrue popularity before that becomes to dire. In the mean time, I'll take care to write the drupal module(s) in a forward compatible way such that it is easy to change the service endpoint later. Best, Matt On Tue, Jun 11, 2013 at 6:29 PM, Rubén Romero <[email protected]>wrote: > Matt, all, > > Den 11. juni 2013 23.11 skrev "Matt Korostoff" <[email protected]> > følgende: > > > > I could take a shot at that, though I'd probably do something more like > > this https://gist.github.com/MKorostoff/5760582 > > > > Would you be comfortable with me contributing this back to the Drupal > > Mobilizer project? Even with a warning like "for experimental use only" > > it's still possible that you'll start to see drupal users pointing their > > production sites at http://www.ducis.net/Miri. Note Mobilizer has close > to > > no usage at the moment, it launched six days ago. > > For developers using ducis is probably fine, but once you get really big > production sites using such a service, it might be better to have a long > term solution. > > Such service would probably be of interest to the Drupal Foundation as > hosting a DeviceMap instance running this code or providing a similar > lookup API on the drupal.org infrastructure is probably a better idea long > term. > > Their site does already use Varnish rather heavily, so providing this > capabilities by adding dClass' VMOD and the DeviceMap DDR for look ups > would not be very hard for them. This infrastructure is also design for > high loads, so it could easily handle the needs of the whole Drupal > ecosystem. At least for a while. > > > > > On Tue, Jun 11, 2013 at 6:22 AM, eberhard speer jr. <[email protected] > >wrote: > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > > > Werner, all, > > > > > > benchmarks etc. > > > Without wanting to start a p*-ing match, here are some of the > > > 'benchmarks' : > > > > > > - - nothing beats Reza's dClass > > > - - my current demo based on the DeviceMap code and a few tweeks (see > > > document on implementation, to be completed) achieves an average of > > > around 20 ms : user-agent parser and resolver (+ ALL available > > > properties per device, property data-type, property default value AND > > > property description) > > > - - the API -- measured over +10 million queries which include junk, > and > > > all manner of user-agent strings -- currently achieves a total > > > processing-time (sever side, from IIS logs) of 100 ms per request > > > > > > It would be nice and constructive if the Drupal Mobilizer could > > > connect/integrate DeviceMap rather then depend on its current device > > > resolution code. It may even be that relying on the demo-API > > > (http://www.ducis.net/Static/examples_php.htm) achieves faster and > > > more detailed results. > > > This would allow the Drupal Mobilizer user to plug-in a local or > > > remote DeviceMap API and use that for the internal HTML formatting. > > > > > > If I were more of a PHP-man, that's something I'd be tinkering with > now. > > > > > > esjr > > > > > > -----BEGIN PGP SIGNATURE----- > > > Version: GnuPG v1.4.8 (MingW32) > > > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > > > > > iQEcBAEBAgAGBQJRtvqAAAoJEOxywXcFLKYcq78IAL7ax87LAAeCQCfhDq9cO8Te > > > Z6G43nYagQtueDt7v/Yb15SSvobct/AQcTUTS7ncEkZwIYHiGxcBFcftzrG9Xz8O > > > toy7uSWicg4Rz8+jCZrv3w6OuxS9ayo/xL+yClXpoT0E7lt27BDKTaksRh9ZkdPH > > > j/glAf/n3+tYnWBwkAIJmEj5QCJCVcrpkoZBNZs1tNE7iUMRx8JZ7BQJeIJRHXOn > > > B78//4imSV2TjgKScax0edqIP1NmqXBm40LjJMybG8P7bwMC2JY+GESVuMUm5R+E > > > PpUnds35yGmmnJsKYBsQ5Zw5rP8UoTfcMMbcUi1n3OMaTzzDttor8X0kbuOKiMk= > > > =a9wH > > > -----END PGP SIGNATURE----- > > > > > Best, > - > Rubén Romero > Varnish Software >
